❦ 24 novembre 2012 15:34 CET, Dominik George <n...@naturalnet.de> :
>> The perfect solution would be a script to migrate from sqlite to MySQL
>> (or PostgreSQL). It does not have to do the actuel migration, just to
>> eat an sqldump from SQLite and turn it into a dump that could be used by
>> MySQL.
>
> So you do not actually plan to have this script run automatically?
No, that would be too much difficult since we are using dbconfig-common.
> I think, as I want to keep the most magical things out for now as it would
> make the unblock process more difficult, that the preinst script should
> actually only dump the database to /var/backups, just as slapd does for
> LDAP when upgrading the package.
Actually, upgrading from a version supporting sqlite to a version not
supporting sqlite leaves the sqlite database untouched. There is no real
data-loss. The data is still here but not usable anymore. We can of
course backup the database in /var/backups but that won't change the
situation of the user.
I have asked people that did successfuly upgrade real sqlite databse to
MySQL if they could provide directions or a script but they don't
remember how they did it exactly. If nobody can come up with a script,
we will just have to put a note in the release notes about this. I
personnaly don't think that there are large installations using SQLite
databases.
--
Don't sacrifice clarity for small gains in "efficiency".
- The Elements of Programming Style (Kernighan & Plauger)
pgpERx14hIJ9k.pgp
Description: PGP signature
