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
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: [Vote] release continuum 1.1 alpha 1
ok, I got it fixed up.. http://people.apache.org/~jmcconnell/continuum/org/apache/maven/continuum/continuum-plexus-runtime/1.1-alpha-1/ that is the tar.gz and it has the license and notice in it so I think we are good to go for this. thanks for all the votes :) I'll let it run a little bit over before I make the vote summary mail jesse On 4/21/07, LAMY Olivier [EMAIL PROTECTED] wrote: Non binding : +1. -- Olivier -Message d'origine- De : Jesse McConnell [mailto:[EMAIL PROTECTED] Envoyé : vendredi 20 avril 2007 21:28 À : continuum-dev@maven.apache.org Objet : [Vote] release continuum 1.1 alpha 1 Its that time, to start releasing continuum in alpha to get some users and feedback on it. The fixes are far too numerous to specify a concise list of, hundred's of jira's fixed and many new additions in functionality. I have it staged at: http://people.apache.org/~jmcconnell/continuum Normal voting rules, 72 hours, +1/0/-1 As wendy mentioned in the thread for preparing this release, a successful vote here will allow me to make an announcement on the continuum users list and I'll move the relevant files to http://people.apache.org/builds/maven/continuum/1.1-alpha-1 +1 from me jesse -- jesse mcconnell [EMAIL PROTECTED] This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. ** Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après le message ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. ** -- 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: [Vote] release continuum 1.1 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: Friday, April 20, 2007 12:28 PM To: continuum-dev@maven.apache.org Subject: [Vote] release continuum 1.1 alpha 1 Its that time, to start releasing continuum in alpha to get some users and feedback on it. The fixes are far too numerous to specify a concise list of, hundred's of jira's fixed and many new additions in functionality. I have it staged at: http://people.apache.org/~jmcconnell/continuum Normal voting rules, 72 hours, +1/0/-1 As wendy mentioned in the thread for preparing this release, a successful vote here will allow me to make an announcement on the continuum users list and I'll move the relevant files to http://people.apache.org/builds/maven/continuum/1.1-alpha-1 +1 from me jesse -- jesse mcconnell [EMAIL PROTECTED]
Re: [Vote] release continuum 1.1 alpha 1
On 4/23/07, Jesse McConnell [EMAIL PROTECTED] wrote: ok, I got it fixed up.. http://people.apache.org/~jmcconnell/continuum/org/apache/maven/continuum/continuum-plexus-runtime/1.1-alpha-1/ that is the tar.gz and it has the license and notice in it so I think we are good to go for this. Thanks, Jesse. With LICENSE and NOTICE present, I'll change my vote to a (non-binding) +0 as I haven't had time to test this distribution. -- Wendy
Re: [Vote] release continuum 1.1 alpha 1
Summary: (binding) +1 (jmcconnell, csanchez, evenisse, rahul, oching, aheritier) (non-binding) +1 (nakees, cgruber, gmisura, jvandermeeren, olamy) (non-binding) +0 (wsmoak, license issue was addressed) I'll get this release migrated out... thanks everyone! jesse On 4/23/07, Misura, Gabriel [EMAIL PROTECTED] wrote: +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: Friday, April 20, 2007 12:28 PM To: continuum-dev@maven.apache.org Subject: [Vote] release continuum 1.1 alpha 1 Its that time, to start releasing continuum in alpha to get some users and feedback on it. The fixes are far too numerous to specify a concise list of, hundred's of jira's fixed and many new additions in functionality. I have it staged at: http://people.apache.org/~jmcconnell/continuum Normal voting rules, 72 hours, +1/0/-1 As wendy mentioned in the thread for preparing this release, a successful vote here will allow me to make an announcement on the continuum users list and I'll move the relevant files to http://people.apache.org/builds/maven/continuum/1.1-alpha-1 +1 from me jesse -- jesse mcconnell [EMAIL PROTECTED] -- 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
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
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.
