A new topic, 'sql tag - Exception not caught ', has been made on a board you
are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=596.new#new
The text of the topic is shown below:
I'm using Liquibase 1.9.5 on SQL Server 2005 and it seems that under a specific
circumstance exceptions are not getting caught from some of my changeSets that
contain a "sql" tag where either the splitstatements or stripcomments
attributes are specified.
When the "sql" tag that contains a SELECT query that is processed successfully,
followed by some other DML statement such as an INSERT statement that fails,
the error raised from the SQL is not caught and reported via Liquibase.
Where I noticed the problem is in a "sql" tag that selects a set of records,
then iterates through the set of records and performs multiple inserts into
several different tables during each iteration. The initial SELECT completes
successfully, but one of my INSERT statements had a hard-to-detect defect that
raised an error on Test database that I was migrating. There was no exception
reported via Liquibase.
The second SQL statement doesn't have to be an insert... A simple way to
replicate the problem is to create a changeSet with the following tag:
<sql stripComments="false">
SELECT count(*) FROM DATABASECHANGELOG;
SELECT count(*) FROM BLAHBLAHBLAH;
</sql>
Any ideas on how to work around this issue so an exception will be caught and
reported? Or is this expected behavior?
tom
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 Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Liquibase-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/liquibase-user
