You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DuckDB has timestamp types with different precisions. We should support conversion from/to those types. TIMESTAMP_NS is probably the most challenging, since postgres does not have a native timestamp type with nanosecond precision. It seems better to truncate/round the nanoseconds to microseconds though than to not support them at all.
Related to #228, which tracks adding TIMESTAMP WITH TIME ZONE.
The text was updated successfully, but these errors were encountered:
For conversion from lets say TIMESTAMP_MS to TIMESTAMP we can abstract it in the TIMESTAMP type in postgres, but to convert it back to the original duckdb type, it might get a little hard to manage with this approach.
Should we create a new type/datum like TIMESTAMP_MS for pg as well?
DuckDB has timestamp types with different precisions. We should support conversion from/to those types.
TIMESTAMP_NS
is probably the most challenging, since postgres does not have a native timestamp type with nanosecond precision. It seems better to truncate/round the nanoseconds to microseconds though than to not support them at all.Related to #228, which tracks adding
TIMESTAMP WITH TIME ZONE
.The text was updated successfully, but these errors were encountered: