Database conversion tool

[Maximilian Kossick]

On Wed, Apr 2, 2008 at 4:33 PM, Ian Monroe <ian at monroe.nu> wrote:
> On Wed, Apr 2, 2008 at 5:26 AM, Maximilian Kossick
>
> <maximilian.kossick at googlemail.com> wrote:
>
> >  For future expansion. I don't think anybody will implement/port the
>  >  necessary code for 2.0, so just assume that the deviceid will always
>  >  be -1. We might have to change the script if we implement it later and
>  >  somebody wants to vonert a A1 database into a post-2.0 database, but
>  >  we can worry about that then.
>  >
>  >  Max
>
>  Well hopefully we can be better about database upgrades paths. So if
>  someone upgrades their 1.4.8 database to 2.0.0, then there would be
>  other code ready to update 2.0.0 to 2.0.1, 2.0.1 to 2.0.2, 2.0.2 to
>  2.1,0 etc.
>
>  Quassel actually has a bunch of numbered .sql files, so if you have
>  database version 34 and you upgrade to Quassel using database version
>  40, it'll run all the .sql files in-between. In Amarok 1.x we did have
>  this sort of thing kind-of, but it'd be nice to have more of a
>  standard clear way of doing it.
>
>  Using just one database backend with full ALTER suppoert will help
>  here. :) I've been in correspondence with the MySQL community
>  relations guy, he says that MySQL 5.1 is going to have one more -rc
>  and then it should be released this summer. 5.1 will be the version
>  with support for in-process databases.
>
>  Ian
>
yay
ALTER support will make our life a lot easier. That sql file idea
sounds pretty good. Depending on the capabilities of mysql, we might
need scripting if we want to do stuff like dynamic collection again,
but we can add that when we have to.

Max