Howdy Robert, Yes - for me that is exactly the point of this - to say 'DO THIS WITH A COPY' and then address the facts of the situation as they are.
Firebird engine went live with the 6.2 release so that horse is already out of the barn, as some would put it. There exists a real desire by a good number of people, for what seems to me reasonable reasons, to remove support for current embedded HSQL database code in an expeditious fashion. This migration assistant piece is something that would be nice but it is not a requirement for many of those using Base files. What would be best now would be to put together some cogent, concise steps for folks to follow in moving off of the embedded HSQL Base file to a new Base file with the database schema and data moved to another system, which could be another embedded Base file using Firebird or could be to an external rdbms. It is also known exactly as to what causes problems for the current, assuming nothing is fixed before release, migration assistant code; so this can tell users check your files for the following and if you don't use any of <these data types/features> run the migration assistant with confidence. If they do have known problem files then offer them steps they can take today, or let them know they should wait for fixes to the migration assistant in later 6.3 releases. At least that is my thoughts. Best wishes Drew On Fri, Jun 7, 2019 at 1:51 PM Robert Großkopf <[email protected]> wrote: > Hi Drew, > > > > In the ESC meeting yesterday the question of including the Migration > > Assistant (MA) feature by default in the pending 6.3 release finished > with > > a decision to do so with one update the UI. Which would show the user a > > link, on the dialog box which starts the process, to a wiki page with > > detailed information on what was possible with MA presently and > information > > on how to perform a migration with or without use of the MA tool. > > Seems there have people decided to do this who didn't use any database > in LO. Migration has many unsolved problems and also the internal > Firebird new bugs, which doesn't exist in HSQLDB ... > And now we should inform how to migrate? I am missing arguments for this > step. > So much databases won't run well when migrating to Firebird with the > Migrating Assistant. I could inform how to migrate, but the first I > would write down: Do all this with a copy of your database and don't > wonder if you are missing views, queries won't run as expected etc. Is > this really the intention of this HowTo? > > Regards > > Robert > -- > Homepage: http://robert.familiegrosskopf.de > LibreOffice Community: http://robert.familiegrosskopf.de/map_3 > > > -- > To unsubscribe e-mail to: [email protected] > Problems? > https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ > Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette > List archive: https://listarchives.libreoffice.org/global/documentation/ > Privacy Policy: https://www.documentfoundation.org/privacy > -- To unsubscribe e-mail to: [email protected] Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
