Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timezone info is lost when applying diff from sqlite to postgres #198

Open
wonder-sk opened this issue Feb 9, 2023 · 2 comments
Open

Timezone info is lost when applying diff from sqlite to postgres #198

wonder-sk opened this issue Feb 9, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@wonder-sk
Copy link
Contributor

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.

@wonder-sk wonder-sk added the bug Something isn't working label Feb 9, 2023
@PeterPetrik
Copy link
Contributor

this is different to #188 right?

@wonder-sk
Copy link
Contributor Author

Yes that one was about not loosing fractional seconds in time/date values

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants