Re: DB schema migration
Hi Erik, Took a look at this - it's not actually the jpox tables (we don't use the pre-configured schema), but problems when we turn on autocreation: In an ALTER TABLE statement, the column 'INTEGER_IDX' has been specified as NOT NULL and either the DEFAULT clause was not specified or was specified as DEFAULT NULL. we also have (which is probably because of our metadata): In an ALTER TABLE statement, the column 'CHANGEDATE' has been specified as NOT NULL and either the DEFAULT clause was not specified or was specified as DEFAULT NULL. So I think I'm going to do the migration tool. - Brett On 24/04/2007, at 7:35 AM, Erik Bengtson wrote: Quoting Brett Porter <[EMAIL PROTECTED]>: 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. If you mean by private tables the JPOX_TABLES, you can drop it and JPOX will automatically recreate if it's needed.
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 >> > >
Re: DB schema migration
Thanks Erik - I'll give that a try ASAP. On 24/04/2007, at 7:35 AM, Erik Bengtson wrote: Quoting Brett Porter <[EMAIL PROTECTED]>: 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. If you mean by private tables the JPOX_TABLES, you can drop it and JPOX will automatically recreate if it's needed.
Re: DB schema migration
Quoting Brett Porter <[EMAIL PROTECTED]>: > 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. > If you mean by private tables the JPOX_TABLES, you can drop it and JPOX will automatically recreate if it's needed.
RE: DB schema migration
FYI, Upgrading from the nightly build, when I dropped continuum.war into jboss deploy, I saw: ERROR 42X14: 'PROFILE_ID_OID' is not a column in table or VTI 'BUILDDEFINITION'. In the log. So I decided I would change my config to use "usersAlpha" and "continuumAlpha" instead of the default (which is what the nightly build was pointing to). So on this page: http://jira.codehaus.org/secure/attachment/26074/continuum_jboss_2.patch I changed "users" to "usersAlpha" and "continuum" to "continuumAlpha". And in ./WEB-INF/classes/META-INF/plexus/application.xml I changed java:comp/env/jdbc/continuumjava:comp/env/jdbc/users To: java:comp/env/jdbc/continuumAlphajava:comp/env/jdbc/usersAlpha And the rest of the instructions (aside from building, since I just grabbed the 1.1alpha1 war directly) from: http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+on+JBoss I'm up and running. Obviously I had to recreate my projects. It seems a bit faster than the previous version (nightly build) I had. Gabriel Misura 20111 120th Ave NE, Cube 2337D Bothell, WA MSN: [EMAIL PROTECTED] Office: 425-288-6217 -Original Message- From: Misura, Gabriel Sent: Monday, April 23, 2007 4:17 PM To: continuum-dev@maven.apache.org Subject: RE: DB schema migration Sounds like this is the answer to my question: Should I start fresh with alpha 1.1? I got nightly build continuum-20070317.00.war to work with Jboss 4.0.5.GA, but I couldn't get the nightly build: continuum-20070418.03.war to work, even when I followed the same instructions at http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+on+JBoss I only have 2 projects so far so seems it would be good for me to start fresh with alpha 1.1. Gabriel Misura 20111 120th Ave NE, Cube 2337D Bothell, WA MSN: [EMAIL PROTECTED] Office: 425-288-6217 -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Monday, April 23, 2007 12:00 PM To: continuum-dev@maven.apache.org Subject: Re: DB schema migration any remaining changes in 1.1 will at _most_ be additive in the form of a boolean value here or there for some improvement, there should be no more changing of column names or anything of that ilk...Those were taken care of in one fel swoop when we fixed things up to remove potential DB keyword conflicts jesse On 4/23/07, Stephane Nicoll <[EMAIL PROTECTED]> 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. > > 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 > > >> > > > > > > > > > -- jesse mcconnell [EMAIL PROTECTED]
Re: DB schema migration
The problems Stephane has is because of the JPOX upgrade, not the schema changes we've made. I'm not saying it won't be possible to migrate from 1.0.3, it just won't come out of the box (or necessarily be ready by the time the release goes out). - Brett On 23/04/2007, at 9:00 PM, Jesse McConnell wrote: any remaining changes in 1.1 will at _most_ be additive in the form of a boolean value here or there for some improvement, there should be no more changing of column names or anything of that ilk...Those were taken care of in one fel swoop when we fixed things up to remove potential DB keyword conflicts jesse On 4/23/07, Stephane Nicoll <[EMAIL PROTECTED]> 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. 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 > >> > > > > > -- jesse mcconnell [EMAIL PROTECTED]
RE: DB schema migration
Sounds like this is the answer to my question: Should I start fresh with alpha 1.1? I got nightly build continuum-20070317.00.war to work with Jboss 4.0.5.GA, but I couldn't get the nightly build: continuum-20070418.03.war to work, even when I followed the same instructions at http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+on+JBoss I only have 2 projects so far so seems it would be good for me to start fresh with alpha 1.1. Gabriel Misura 20111 120th Ave NE, Cube 2337D Bothell, WA MSN: [EMAIL PROTECTED] Office: 425-288-6217 -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Monday, April 23, 2007 12:00 PM To: continuum-dev@maven.apache.org Subject: Re: DB schema migration any remaining changes in 1.1 will at _most_ be additive in the form of a boolean value here or there for some improvement, there should be no more changing of column names or anything of that ilk...Those were taken care of in one fel swoop when we fixed things up to remove potential DB keyword conflicts jesse On 4/23/07, Stephane Nicoll <[EMAIL PROTECTED]> 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. > > 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 > > >> > > > > > > > > > -- jesse mcconnell [EMAIL PROTECTED]
Re: DB schema migration
any remaining changes in 1.1 will at _most_ be additive in the form of a boolean value here or there for some improvement, there should be no more changing of column names or anything of that ilk...Those were taken care of in one fel swoop when we fixed things up to remove potential DB keyword conflicts jesse On 4/23/07, Stephane Nicoll <[EMAIL PROTECTED]> 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. 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 > >> > > > > > -- jesse mcconnell [EMAIL PROTECTED]
Re: DB schema migration
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. 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
Hi, On 4/23/07, Brett Porter <[EMAIL PROTECTED]> wrote: This is definitely one for the release notes, btw. alpha-1 will not work with 1.0.3 (or earlier 1.1 snapshot) databases. Too bad. Honestly, this will be a show stopper for people already using 1.0.3 (or 1.1-SNAPSHOT like me). Thanks for handling this anyway. Stéphane - 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
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
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 >
