Every changeset is uniquely identified based on its ID, author and by the changelog name. The databasechangelog element also has an attribute (logicalFilePath) which you can use to make the changelog name consistent. If the logicalFilePath was different for each Changelog then the changesets will not clash in any way.
Paul ----- Original Message ---- From: LiquiBase Community Forum <[email protected]> To: [email protected] Sent: Wednesday, 17 June, 2009 2:22:44 Subject: [Liquibase-user] New Topic: Running multiple different change sets. A new topic, 'Running multiple different change sets.', has been made on a board you are watching. You can see it at http://liquibase.org/forum/index.php?topic=50.new#new The text of the topic is shown below: Hi. I might have a situation where I have several sub-projects, each with their own set of liquibase scripts, which coexist in the same database. Does this cause problems for liquibase if I'm running updates from project A, and then a completely separate set of updates from project B? (Assuming their schemas don't interfere with each other of course.) Does liquibase handle this? BTW, I've noticed in the manual the list of Available Database Refactorings is only available on the home page, not in the table of contents sidebar, which is a bit annoying, and made me hunt around a lot looking for them before I figured it out. Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=1.0 Regards, The LiquiBase Community Forum Team. ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Liquibase-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/liquibase-user
