Since my local MySQL session runs in IST, it automatically added +5:30, shifting all timestamps. 🪩 𝗜𝗺𝗽𝗮𝗰𝘁 Because my query relied on a monthly date range: start_time >= '2025-11-01' AND ...

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 ...

The TO_DATE function, for some reason, does not cast to DATE data-type. Instead, it is just an alias for TIMESTAMP_FORMAT. Also, if the host variable isn't a character data type, you have to wrap the ...

create table "my_table" ( "id" int4 primary key generated always as identity, "created_time" TIMESTAMP WITHOUT TIME ZONE not null default current_timestamp, "created_by" text not null ); ERROR ...