You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2007/03/14 12:16:25 UTC

DO NOT REPLY [Bug 41836] - No warning from SQL task, but jdbc gets SQL State: 23000

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41836>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=41836





------- Additional Comments From stevel@apache.org  2007-03-14 04:16 -------
I think the problem here is that <sql> on cares about errors; it doesnt look for
and print warnings. We could correct this in two ways

1. log the warnings at INFO or WARN
2. add a failOnWarning attribute to trigger behaviour on warnings

Would this work?

As an aside, we have zero unit tests against mysql, but as I've been automating
deployment of mysql at work, I may know how we could do this, though the test
setup would be tricky indeed. We'd need JMX, the (GPL) Mysql JMX connector, and
SmartFrog, plus the configuration info for the target test system(s), and we'd
need to get smartfrog to run an antunit build file. Much, much easier to test
against HSQLDB instead.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org