[Libreoffice-bugs] [Bug 119675] Firebird: Migration: User dialog to set treatment of datetime and time values during migration

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Tue Dec 11 19:12:10 UTC 2018


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

--- Comment #2 from Terrence Enger <lo_bugs at iseries-guru.com> ---
[1] says that Firebird 4.0 Beta1 will have TIME WITH TIMEZONE and
DATETIME WITH TIMEZONE.  Firebird 4.0 is still alpha, and I have not
found a schedule for its advancement from that state.  The latest
"daily" build of 4.0, [2], was on 2018-11-25, which is earlier than
the commit in question.

I wonder whether this promise from Firebird should change our plans
with respect to this bug and bug 117732?

In the long run, I expect that we can most nearly maintain the
behaviour that users are familiar with by:
(1) Our conversion from HSQLDB converts to fields with-timezone-GMT.
(2) We translate data retrieved from the database to local time and we
    convert data writtem to the database to GMT.

Do we expect to do that?  Should this change our plans with respect to
always offering the conversion from embedded HSQLDB to embedded
Firebird?

Of course, after doing (2), it will be tempting to give the user
access to additional functionality by optionally--or, optionally if
the .odb was converted from embedded HSQLDB--giving the user some
explicit access to timezone data.  I do not know what this might look
like.  Do we have anything like this in our connection to a database
already offering with-timezone?

references
----------
[1]
<http://tracker.firebirdsql.org/browse/CORE-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel>
[2] <http://web.firebirds1l.org/download/snapshot_builds/linux/fbtrunk>

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20181211/dcb7894b/attachment.html>


More information about the Libreoffice-bugs mailing list