the current behavior of ODBC is that it ignores the time zone field in Timestamp data, assumes all timestamp data is UTC during interpretation. The Arrow compute library should be able to handle ...
We discovered a wrong result returned by the equality operator when comparing a date and a timestamp when the date operand is explicitly casted, but not the timestamp: import java.sql.Connection; ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results