Date: prev next · Thread: first prev next last
2018 Archives by date, by thread · List index

Hi *,

have tested this kind of migration:

Downloaded the daily build of 2018-04-11,
Opened the database, which is part of the Base Handbook:
No comment like "Internal HSQLB" apperas at the bottom of the window.
Tried to open the tablecontainer.
No table apperas, but after some time the following message:

Connection to datasource "Media_without_Macros" couldn't be established.

firebird_sdbc error:
*Dynamic SQL Error
*SQL error code = -104
*Token unknown - line 1, column 163
caused by

I haven't set the experimental features to "yes". I wasn't asked if I
want to change the database from HSQLDB to Firebird.

Base should never be a playground for such a function. People will loos
their data and will never again use LO after starting one database with
this automatic.

1. An automatic migration should never be installed from a working
internal database to a database, which is an "experimental feature"
(Firebird) - and never means: also never with a daily build.
2. A migration should only be offered, never automatically, when
internal Firebird database has been activated.
3. The migration should create a new database with the migrated content,
not overwrite the old database.


LibreOffice Community:

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.