<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Firebird-migration must happen only after user consent and advise to backup data prior to migration at 6.1" href="https://bugs.documentfoundation.org/show_bug.cgi?id=116944#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Firebird-migration must happen only after user consent and advise to backup data prior to migration at 6.1" href="https://bugs.documentfoundation.org/show_bug.cgi?id=116944">bug 116944</a> from <a class="email" href="mailto:lionel@mamane.lu" title="Lionel Elie Mamane <lionel@mamane.lu>"> Lionel Elie Mamane</a> <pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=116944#c11">comment #11</a>) > There is ESC support for the implementation (Lionel is a member) There is ESC support for the migration, and the change of default, but not for the timing of it. HSQLDB and Firebird are two different systems with two different SQL syntaxes, different feature sets, etc. People that use Base as a development platform to make their own application need a transition period to adapt their code. IMO, the timing of the change of default for *new* databases is still not decided for certain. It might happen for the next release, or later. Depends on when bugs like 104918, 116935 and 116936 are fixed. See bug 51780 for the tracking of that. We may also want to wait for <a class="bz_bug_link bz_status_NEW " title="NEW - Firebird SDBC should implement XRowUpdate interface" href="show_bug.cgi?id=116936">bug 116936</a> to be fixed. Removing HSQLDB needs _time_ from the moment Firebird-in-LibreOffice is stable, good quality, and has - broadly speaking - feature-parity with HSQLDB. Bugs like 116936 are blocker for that. See <a class="bz_bug_link bz_status_NEW " title="NEW - [META] HSQLDB removal blockers" href="show_bug.cgi?id=116970">bug 116970</a> for the tracking of that. > rather than stretching out the migration of internal HSQLDB to Firebird > if the migration code is ready and gets well tested, there really is no > practical UX reason to stretch out the pain point of the DB transition. I feel that this POV comes from a view that all SQL engines are interchangeable, they only differ in on-disk data storage format. For users that only use Base as a graphical GUI to do stuff, that may even be, to a moderate to large degree, true. However, for people using Base as an application development platform, that is very much not true.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>