MS SQL Server 2005 Liquibase 1.9.0 We use ant target updateDatabase for our development changes, and promote our changes using ant target updateDatabase with parameter outputFile to generate a file to submit to dba's.
We set runOnChange="true" on our changeSet. The generated sql produces : UPDATE [dbo].[DATABASECHANGELOG] SET ... WHERE ID = 'idxxx'... if the changeSet has already been executed. When we promote the sql (qa, uat, prod, etc), the changeSet may or may not have been executed. If not, the Update [dbo].[DATABASECHANGELOG] will update a row that is not there yet. Of course, we could generate sql by running updateDatabase with parameter outputFile for each environment, but we would prefer not to do that for security and testing reasons. Can we request a modification to have the generated sql be: If exists(....) Delete From [dbo].[DATABASECHANGELOG] SET ... WHERE ID = 'idxxx' Insert Into [dbo].[DATABASECHANGELOG] SET ... instead of UPDATE [dbo].[DATABASECHANGELOG] SET ... WHERE ID = 'idxxx'...? I apologize if this is the wrong forum for this request. Thanks! -- View this message in context: http://www.nabble.com/runOnChange%3D%22true%22-tp22250175p22250175.html Sent from the LiquiBase - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Liquibase-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/liquibase-user
