A new topic, 'is tag logic correct?', has been made on a board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=662.new#new
The text of the topic is shown below:
if i create a <tag> to begin a changeset (to give me rollback point), it will
applied to the row PRIOR to the current changeset, in databasechangelog.
This row may not have the same filename as the current changeset file.
Now, if i then try to rollback the entire changeset, only the rows with the
same filename of the current changeset will be deleted.
If the tag (for the current changeset) has been applied to the last row of the
prior changeset, the rollback command will not find it, and my
databasechangelog will still contain the tag.
This doesn't seem correct to me.
Should not the tag be stored as the first row of the current changeset, and
accordingly, deleted in the event of rollback?
mr
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.
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Liquibase-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/liquibase-user
