Vivek Nakeesan is out of the office.
I will be out of the office starting 25/04/2007 and will not return until 26/04/2007. I will respond to your message when I return.
Re: DB schema migration
Hi, On 4/25/07, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: Stephane Nicoll wrote: > Can I be sure at least that the DB model won't change as from alpha-1? > If so I can maybe drop completely my database and recreate my > projects. We've been over this before, but I'll repeat: Alphas give no guarantee of API (including DB) stability. Hopefully it won't change too much, but it should in no way stop the developers from breaking stuff. I agree. What is important here is the ability to dump the database to an external DB file (xml would be a natural choice) which can be read by a newer Continuum. As soon as this is in place, I'll migrate. Cheers, Stéphane Hopefully 1.1 will be pretty stable so it can be released ASAP and bugs can be fixed on a 1.1.x branch. -- Trygve > > Thanks, > Stéphane > > On 4/23/07, Brett Porter <[EMAIL PROTECTED]> wrote: >> This was one of the things I was going to try and have done before >> alpha-1 - I just forgot. >> >> Erik - the problem in upgrading is the changes in private tables >> between versions of jpox that we hadn't given explicit names to. We'd >> probably appreciate most help in future proofing our jpox use a bit >> more in case it's internal schema changes again. >> >> I already have the tools to do an xml export of the old tables, it >> just needs to somehow be set to run in dump mode using the old jpox, >> and import using the new one. I'll look at that during ApacheCon, I >> think. If anyone else wants to take the task while I'm on holidays, >> let me know... we should also make the tool work with 1.0.3 databases >> if possible. >> >> This is definitely one for the release notes, btw. alpha-1 will not >> work with 1.0.3 (or earlier 1.1 snapshot) databases. >> >> - Brett >> >> On 22/04/2007, at 2:10 PM, Erik Bengtson wrote: >> >> > If you guys need some tooling from JPOX, let me know and I could >> > plan to >> > implement some kind of "export" to XML, and "import" from XML. In >> > between >> > export/import you could apply Xqueries to transform data to match >> > the new >> > schema >> > >> > Quoting Stephane Nicoll <[EMAIL PROTECTED]>: >> > >> >> Hi, >> >> >> >> I'm currently running a 1.1-SNAPSHOT from February which runs ok >> >> except a few minor issues. I'd like to upgrade to 1.1 alpha 1 as soon >> >> as it's out to provide feedback & co. >> >> >> >> Last time I tried to upgrade, I had to revert because the model >> >> schema >> >> has changed and it was really difficult to update my existing >> >> data. Is >> >> there something scheduled for alpha1 regarding this (at least a >> >> manual >> >> procedure to upgrade my schema if necessary). >> >> >> >> Thanks, >> >> Stéphane >> >> >> > >> > >>
Re: DB schema migration
Stephane Nicoll wrote: Can I be sure at least that the DB model won't change as from alpha-1? If so I can maybe drop completely my database and recreate my projects. We've been over this before, but I'll repeat: Alphas give no guarantee of API (including DB) stability. Hopefully it won't change too much, but it should in no way stop the developers from breaking stuff. The database is in particular something that can, and most likely will change in one form or another. The only thing that's supposed to be stable in Continuum are the remote interfaces (socket and xml-rpc stuff) and the internal notification APIs. What is important here is the ability to dump the database to an external DB file (xml would be a natural choice) which can be read by a newer Continuum. Hopefully 1.1 will be pretty stable so it can be released ASAP and bugs can be fixed on a 1.1.x branch. -- Trygve Thanks, Stéphane On 4/23/07, Brett Porter <[EMAIL PROTECTED]> wrote: This was one of the things I was going to try and have done before alpha-1 - I just forgot. Erik - the problem in upgrading is the changes in private tables between versions of jpox that we hadn't given explicit names to. We'd probably appreciate most help in future proofing our jpox use a bit more in case it's internal schema changes again. I already have the tools to do an xml export of the old tables, it just needs to somehow be set to run in dump mode using the old jpox, and import using the new one. I'll look at that during ApacheCon, I think. If anyone else wants to take the task while I'm on holidays, let me know... we should also make the tool work with 1.0.3 databases if possible. This is definitely one for the release notes, btw. alpha-1 will not work with 1.0.3 (or earlier 1.1 snapshot) databases. - Brett On 22/04/2007, at 2:10 PM, Erik Bengtson wrote: > If you guys need some tooling from JPOX, let me know and I could > plan to > implement some kind of "export" to XML, and "import" from XML. In > between > export/import you could apply Xqueries to transform data to match > the new > schema > > Quoting Stephane Nicoll <[EMAIL PROTECTED]>: > >> Hi, >> >> I'm currently running a 1.1-SNAPSHOT from February which runs ok >> except a few minor issues. I'd like to upgrade to 1.1 alpha 1 as soon >> as it's out to provide feedback & co. >> >> Last time I tried to upgrade, I had to revert because the model >> schema >> has changed and it was really difficult to update my existing >> data. Is >> there something scheduled for alpha1 regarding this (at least a >> manual >> procedure to upgrade my schema if necessary). >> >> Thanks, >> Stéphane >> > >
