https://bugs.documentfoundation.org/show_bug.cgi?id=117732

--- Comment #10 from Drew Jensen <drewjensen.in...@gmail.com> ---
(In reply to Tamas Bunth from comment #8)
> This can be related:
> 
> https://bugs.documentfoundation.org/show_bug.cgi?id=63566

Part of it is.

So - today I can migrate that table using the current Base import functionality
(hsqldb:sdbc) source data to (firebird:sdbc) target data and date, time and
timestamp all transfer without any APPARENT change in values. Truth is the
values changed.

As the other issue points out a feature of HSQLdb is to store time values as
the UTC+0 time and accounts (changes) the time representation supplied from the
user based on the users local time zone, later when it supplies a time
representation for the value it again accounts for the users local time zone -
users in different time zones see the 'time' in their time zone, the value
stored never changed.

Firebird doesn't know how to do that at the moment. Users in different time
zones reading the value will see identical time representations but they are
one their own to deal with the fact the time they are seeing may be from the
perspective of a different time zone from their time zone. (note; from scanning
their bug/ticket tracker it looks like that (support time zones) is in the
works and possibly in one of the minor 3.x releases, but I didn't drill down to
see if that means going to a common storage tz (UTC+0).

You can see it all at work today on your desktop. 

It took the example hsql file attached here and moved the table into a firebird
odb using the Base import routine. When that is finished it looks like the data
moved without change. But then I change the time zone for my OS and voila the
HSQLdb and firebird ODB files show they actually have different data values in
the table.  (will attach a couple of scree shots showing that)

IDK what the right answer is here - the only way to not loose the old data is
to move the UTC+0 value into the firebird table, but then the display will
change for all users not in the UTC+0 time zone. 

But that only accounts for some of the change that is happening - for the rest
it is something else.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to