Open GoogleCodeExporter opened 9 years ago
Then there is also a similar problem in Briefcase, when it does the shift to
the exporting machine's time zone. If you are exporting in the same time zone
as Collect, the one missed shift effectively undoes the problem created by the
other missed shift. But if you are collecting and exporting in different time
zones, then the "never shifting the date" approach fails in cases where
midnight is passed in one shift but not the other.
This is a painful problem to fix, because data sitting on the server is
effectively corrupted (the date-time fields are wrong). Fixing both the server
and Briefcase at the same time leaves still the corrupted data -- and, worse,
somebody who was collecting and exporting in the same time zone can see a
problem suddenly appear only after the fix, for old data sitting on the server.
Original comment by chrislro...@gmail.com
on 6 Oct 2014 at 10:19
Original issue reported on code.google.com by
m.margar...@synergo.gr
on 6 Oct 2014 at 6:32