Hi, I’m using the liquibase maven plugin 2.0.2. Everything seems to work as advertised, except for unexpected behavior with tagging the database.
Let’s say I have three changelog xml files, and each one contains a with a single tagDatabase tag. Each tagDatabase tag is specified with tag=“1.1”, tag=“1.2”, tag=“1.3”. I run them all in sequence with mvn liquibase:update, and then inspect the database. I’d expect to see three rows in the databasechangelog table, each with a different tag. Instead what I see is three rows with id/author/etc as expected, but they ALL have a tag of 1.3, not one with 1.1, one with 1.2, and one with 1.3.
How can I specify a different tag for each changelog file so that sets of changes can be tagged and rolled back?
Thanks,
Jason
So you have just a changelog with commands in it? Or are there other change tags in there as well?
I have been able to partially re-create this using MySQLhttp://www.liquibase.org/xml/ns/dbchangelog ”http://www.w3.org/2001/XMLSchema-instance ”http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-2.0.xsd ”>http://www.liquibase.org/xml/ns/dbchangelog ”http://www.w3.org/2001/XMLSchema-instance ”http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-2.0.xsd ”>
DEBUG 10/25/11 10:27 PM:liquibase: Connected to root@localhost@jdbc:mysql://localhost:3306/testLOCKED FROM DATABASECHANGELOGLOCK WHERE ID=1DATABASECHANGELOGLOCK SET LOCKED = 1, LOCKEDBY = ‘texas (192.168.1.105)’, LOCKGRANTED = ‘2011-10-25 22:27:49.671’ WHERE ID = 1 AND LOCKED = 0DATABASECHANGELOG WHERE MD5SUM IS NOT NULLDATABASECHANGELOGDATABASECHANGELOG ORDER BY DATEEXECUTED ASC, ORDEREXECUTED ASCDATABASECHANGELOGDATABASECHANGELOG ORDER BY DATEEXECUTED ASC, ORDEREXECUTED ASCDATABASECHANGELOG SET TAG = ‘2.1’ WHERE DATEEXECUTED = (SELECT MAX(DATEEXECUTED) FROM (SELECT DATEEXECUTED FROM DATABASECHANGELOG) AS X)DATABASECHANGELOGDATABASECHANGELOG (AUTHOR, COMMENTS, DATEEXECUTED, DESCRIPTION, EXECTYPE, FILENAME, ID, LIQUIBASE, MD5SUM, ORDEREXECUTED, TAG) VALUES (‘mmiller (generated)’, ‘’, NOW(), ‘Tag Database’, ‘EXECUTED’, ‘D:/eclipseworkspace/workspace/LiquibaseTest/tagDB1.xml’, ‘1315971950477-71’, ‘2.0.2-SNP’, ‘3:3c71dc51ad47d7809e4aadb9ba55849d’, 7, ‘2.1’)DATABASECHANGELOG SET TAG = ‘1.2’ WHERE DATEEXECUTED = (SELECT MAX(DATEEXECUTED) FROM (SELECT DATEEXECUTED FROM DATABASECHANGELOG) AS X)DATABASECHANGELOG (AUTHOR, COMMENTS, DATEEXECUTED, DESCRIPTION, EXECTYPE, FILENAME, ID, LIQUIBASE, MD5SUM, ORDEREXECUTED, TAG) VALUES (‘mmiller (generated)’, ‘’, NOW(), ‘Tag Database’, ‘EXECUTED’, ‘D:/eclipseworkspace/workspace/LiquibaseTest/tagDB2.xml’, ‘1315971950477-72’, ‘2.0.2-SNP’, ‘3:8cc9fd308853023cf952017be45d7a30’, 8, ‘1.2’)DATABASECHANGELOG SET TAG = ‘2.3’ WHERE DATEEXECUTED = (SELECT MAX(DATEEXECUTED) FROM (SELECT DATEEXECUTED FROM DATABASECHANGELOG) AS X)DATABASECHANGELOG (AUTHOR, COMMENTS, DATEEXECUTED, DESCRIPTION, EXECTYPE, FILENAME, ID, LIQUIBASE, MD5SUM, ORDEREXECUTED, TAG) VALUES (‘mmiller (generated)’, ‘’, NOW(), ‘Tag Database’, ‘EXECUTED’, ‘D:/eclipseworkspace/workspace/LiquibaseTest/tagDB3.xml’, ‘1315971950477-73’, ‘2.0.2-SNP’, ‘3:11cb9cfa85f6f563fa740860e685c0ed’, 9, ‘2.3’)DATABASECHANGELOGLOCK SET LOCKED = 0, LOCKEDBY = NULL, LOCKGRANTED = NULL WHERE ID = 1
In my small test case, I think the problem comes from the following statementDATABASECHANGELOG SET TAG = ‘2.3’ WHERE DATEEXECUTED = (SELECT MAX(DATEEXECUTED) FROM (SELECT DATEEXECUTED FROM DATABASECHANGELOG) AS X)
Guest
October 26, 2011, 4:05am
5
I’m getting it set up to use with an existing database, so my intent is to have one changelog with one tag command in it to tag the initial state, and subsequent changelogs with other commands (changesets) but each ending with a tag changeset. I’ve tried this with and without other changesets along with the tags. I’m using MySQL.
So there’s an “orderexecuted” tag I can use? Would that ensure that the tags are correctly inserted? Or if this is really problematic should I only run one changeset/tag per mvn liquibase:update? I’d kindof expect to be able to take an initial schema and run liquibase:update on it and have an arbitrary number of files/changesets and tags applied though.
