A new topic, 'Unexpected behaviour of preconditions with updateSQL', has been
made on a board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=415.new#new
The text of the topic is shown below:
Hi
I'm using Liquibase 2.0-dev and have an issue with how preconditions are
evaluated in updateSQL mode.
I'd expect that preconditions are evaluated and changesets get written to the
SQL output file similar to when
they a changelog is applied to the database directly but that's not the case.
By default, preconditions are
ignored when in updateSQL mode.
I noticed that you can set an attribute 'onSqlOutput' on <preConditions> to one
of [TEST|FAIL|IGNORE] whereas
IGNORE is the default. What is the difference between FAIL and TEST? I couldn't
see any.
How about changing the default behaviour to TEST (and set a default in the XSD
as well) to be consistent
with the known update behaviour?
Cheers, Felix
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.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Liquibase-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/liquibase-user
