This enhancement request is to add, in the dialog which pops up when an HSQL connection is created, a URLpointing to a TDF wiki page that covers: What is happening? HSQL is going away Instructions on how to migrate their data out of the HSQL sdbc Base file. The migration could be using the Migration Assistant. It could be to move their data to an external database. There should be instructions on how to migrate to an Firebird sdbc file without the migration assistant as well as with it. The wiki page should be setup for native language translations.
I agree with this. However, considering all the migration pb, Firebird should be back experimental.
Yep, this would be most useful. Shouldn't absolve the project of actually having a migration assistant that works correctly though before we make FB the default. My guesstimate is that the migration assistant only fully works correctly for less than 30% of all current in-the-wild hsqldb embedded ODB files.
Here are more information about problems related to migration: https://wastack.wordpress.com/2018/07/25/database-migration-in-libreoffice-bug-fixes-and-more/
(In reply to Alex Thurgood from comment #2) > Yep, this would be most useful. Shouldn't absolve the project of actually > having a migration assistant that works correctly though before we make FB > the default. > > My guesstimate is that the migration assistant only fully works correctly > for less than 30% of all current in-the-wild hsqldb embedded ODB files. But the Firebird sdbc became available without experimental features turned on and the default choice in the type dropdown box with the 6.2 release.
Caolán McNamara dropped code for this into gerritt this afternoon and notified the dev ML: "On this, my patch at https://gerrit.libreoffice.org/#/c/73610/ would add such a link to the migration warning pointing provisionally to the blank page https://wiki.documentfoundation.org/Documentation/HowTo/MigrateFromHSQLDB which someone else would have to fill in." The migration assistant dialog will be active with 'Later' as the default choice. Will talk with the documentation team to see to it the page is setup properly for native language support.