<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Base "Confirm Migration" message pops up everytime via macro" href="https://bugs.documentfoundation.org/show_bug.cgi?id=121587#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Base "Confirm Migration" message pops up everytime via macro" href="https://bugs.documentfoundation.org/show_bug.cgi?id=121587">bug 121587</a> from <a class="email" href="mailto:iplaw67@tuta.io" title="Alex Thurgood <iplaw67@tuta.io>"> Alex Thurgood</a> <pre>(In reply to Tamas Bunth from <a href="show_bug.cgi?id=121587#c4">comment #4</a>) > There are still two alternatives: > > - The migration assistant runs silently for all the HSQL databases it > touches. > > - No migration > > Which one would be better? IMO, no migration. Someone who programs access to an hsqldb embedded ODB via macro programming could be said to be supposed to know that the move to Firebird as default is underway - thus, if the db hasn't yet been migrated, the macro developer has deliberately planned it that way, and decided to stick with hsqldb (at least until such time as they decide to migrate to Firebird out of choice and adapt the macro to deal with that). At worst, what happens if no migration occurs ? The user continues to be able to use the database as before, and the macro continues to work as planned by the original developer of the macro program.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>