DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24668>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24668 SQL task's onError='stop' behaviour doesn't match docs ------- Additional Comments From [EMAIL PROTECTED] 2003-11-26 12:39 ------- implementation and documentation are quite ambiguos to me. abort -> explicit rollback + fail continue -> only log exception, commit what we have at end of transaction, no fail stop docs are not clear at all stop implementation -> exactly identical to abort just that the rollback doesn't happen explicitly. But the transaction won't be committed either. My interpreation of the docs (and what probably is desired behavior) would be to rollback the transaction, don't run consecutive transactions but don't make the task fail. This seems to be the same as your interpretation. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
