A new topic, 'Differences between 2.0-RC2 and 2.0-RC3', has been made on a
board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=621.new#new
The text of the topic is shown below:
Hi Nathan,
As you see I've been trying RC3 and I saw a different behavior compared with
RC2.
1 - If you have a change set like this:
Code:
<changeSet id="test-inserts" author="alexis">
<delete tableName="test_table"></delete>
<sqlFile path="test.sql" />
</changeSet>
And test.sql is:
Code:
insert into test_table values(1, 'hello');
insert into test_table values(2, 'hello');
You run that and after that you modify the sql, instead of fail like in RC2 it
does nothing. Not even a warning saying that the check-sum has changed.
Is this the new way of not fail when a changeset has been accidentally modified?
2 - If you run a change-set using RC2 that has runOnChange="true" and then you
run the same thing but using RC3 it tries to execute that even when the
changeset hasn't changed in content. So it detects that the check-sum is
different while nothing has actually be modified in it.
Is this the correct behavior? and will it happen every time we update liquibase
version?
Thanks a lot,
Alexis.
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.------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
Liquibase-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/liquibase-user
