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
I have a table with DATETIME column type containing a value with timezone info. When doing a copy to postgres, the timezone info is lost - and mergin-db-sync reports that there is an issue in geodiff.
2022/11/04 02:50:27.305+02 -- original value in sqlite
2022-11-04 02:50:27.305 -- what gets stored in postgres (we're using "timestamp without time zone" type)
2022-11-04T02:50:27.305Z -- when we do copy back from postgres to sqlite
A workaround for now is not to use date/time values with timezone info.
The text was updated successfully, but these errors were encountered:
I have a table with
DATETIME
column type containing a value with timezone info. When doing a copy to postgres, the timezone info is lost - and mergin-db-sync reports that there is an issue in geodiff.A workaround for now is not to use date/time values with timezone info.
The text was updated successfully, but these errors were encountered: