Liquibase Community Forum
2010-12-16 15:43:23 UTC
A new topic, 'generateChangeLog and empty <rollback/> tags', has been made on a board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=840.new#new
The text of the topic is shown below:
The Liquibase documentation states that create table, rename column, and add column can all automatically generate rollback statements if they are the only items in a changeSet.
When you run generateChangeLog from the command line against a template database, every changeSet that is created in the xml file has an empty <rollback/> tag added to it. If I'm reading the documentation correctly, that means that those changeSets will not roll back properly even though Liquibase can handle most of them automatically without any problem.
Is there any way to suppress that empty <rollback/> tag on changeSets that only contain create table, rename column, and add column refactorings?
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.
You can see it at
http://liquibase.org/forum/index.php?topic=840.new#new
The text of the topic is shown below:
The Liquibase documentation states that create table, rename column, and add column can all automatically generate rollback statements if they are the only items in a changeSet.
When you run generateChangeLog from the command line against a template database, every changeSet that is created in the xml file has an empty <rollback/> tag added to it. If I'm reading the documentation correctly, that means that those changeSets will not roll back properly even though Liquibase can handle most of them automatically without any problem.
Is there any way to suppress that empty <rollback/> tag on changeSets that only contain create table, rename column, and add column refactorings?
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.