https://bugs.documentfoundation.org/show_bug.cgi?id=116944
--- Comment #23 from robert@familiegrosskopf.de ---
(In reply to Lionel Elie Mamane from comment #21)
Deprecation when Firebird is in good shape (cf the
tracker bug for that), and removal at least one major distro LTS cycle after
that.
--> New databases will be created with Firebird (by default?) in 6.1
_If_ the Firebird driver is in a good enough shape, which we have good hope
it will be.
- Why keep the old data in the file?
--> Creating a new file with just Firebird data makes more sense as the
end user is not able to recover the data!
Yes.
- Why do we need to get rid of HSQLDB so quickly?
We don't.
This would be the best solution.
Changing step by step. Let us first try to get Firebird better working than
HSQLDB for a normal user. Do not deprecate HSQLDB before. Test the migration.
Migration has to save all: Tables, relations and views. Could be views will be
saved as queries, if code is to complicated. After this is working we should
set HSQLDB as deprecated.
I have seen the long time for getting Firebird to work in Base - experimental
since LO 4.2! We will need also time for a well working Firebird as non
experimental database.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 116944] Firebird-migration must happen only after user consent and advise to backup data prior to migration at 6.1 · bugzilla-daemon
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.