Nope those changesets ids have remained the same. The way I understand it is that, If I wanted to re-run a changed changesets after making changes, then I'd add the <validChecksum> tag. otherwise, I don't want to re-run that changeset.
--- Regards, Saptarshi PURKAYASTHA My Tech Blog: http://sunnytalkstech.blogspot.com You Live by CHOICE, Not by CHANCE On 14 September 2011 20:21, Darius Jazayeri <[email protected]> wrote: > Saptarshi, isn't the problem that you edited an existing changeset without > giving multiple allowed-checksum values? > > -Darius > > > On Wed, Sep 14, 2011 at 7:33 AM, Saptarshi Purkayastha > <[email protected]>wrote: > >> From the Liquibase v2 Upgrade help <http://www.liquibase.org/v2_upgrade>: >> >> * >> >> Liquibase stores checksums for each change executed in the >> DATABASECHANGELOG table. These checksums are used to alert the user to >> changeSets that have been changed after they were executed, and to handle >> runOnChange=“true” changeSets. >> >> The way we compute these checksums changed in 2.0. The first time you >> update an existing database, Liquibase will detect the old format and >> upgrade the checksum values. During this first run, Liquibase will not be >> able to detect modified changeSets or runOnChange requirements. If you are >> concerned about this, you may want to run a known unchanged changelog >> against the database with 2.0 before updating your new changelog. >> * >> But I'm not sure if that'll help... I've tried replicating how that error >> happens, but the checksum generation today seems so quick that I'm unable to >> stop in its tracks. :| and things are working fine >> >> --- >> Regards, >> Saptarshi PURKAYASTHA >> >> My Tech Blog: http://sunnytalkstech.blogspot.com >> You Live by CHOICE, Not by CHANCE >> >> >> On 14 September 2011 17:48, Ben Wolfe <[email protected]> wrote: >> >>> Is there a way to replicate this and then write something to prevent >>> it Saptarshi? >>> >>> Ben >>> >>> On Wed, Sep 14, 2011 at 5:25 AM, Saptarshi Purkayastha <[email protected]> >>> wrote: >>> > I'm afraid I've seen this after the liquibase 2.0 upgrade fairly often >>> > because of the ways in which checksum generation has changed... >>> > This has happened to me when the installation/upgrade has not completed >>> > correctly... and then on resuming the upgrade/installation, this error >>> is >>> > thrown >>> > Joel, did your installation/upgrade stop prematurely before?? >>> > --- >>> > Regards, >>> > Saptarshi PURKAYASTHA >>> > >>> > My Tech Blog: http://sunnytalkstech.blogspot.com >>> > You Live by CHOICE, Not by CHANCE >>> > >>> > >>> > On 14 September 2011 07:38, Joel Tellez <[email protected]> wrote: >>> >> >>> >> Hello all, I just wanted to let you know that I tried starting the app >>> >> and I received the following message. >>> >> >>> >> ERROR - Listener.contextInitialized(154) |2011-09-13 18:41:06,725| Got >>> >> exception while starting up: >>> >> java.lang.RuntimeException: Error occurred while trying to get the >>> >> updates needed for the database. Validation Failed: >>> >> 2 change sets check sum >>> >> liquibase-update-to-latest.xml::20090122-0853::bwolfe is >>> >> now: 3:500ce2e46732bad3a7b2e617a25a3710 >>> >> liquibase-update-to-latest.xml::20090214-2247::isherman is >>> >> now: 3:8e95edd3fc7ba6c9f124b0e14536bd4b >>> >> >>> >> Thanks, >>> >> >>> >> -Joel >>> > >>> > ________________________________ >>> > Click here to unsubscribe from OpenMRS Developers' mailing list >>> >> >> ------------------------------ >> Click here to >> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >> OpenMRS Developers' mailing list >> > > _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
