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=40889>. 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=40889 ------- Additional Comments From [EMAIL PROTECTED] 2006-12-21 13:56 ------- I'm not a log4j developer, but happened to be looking at this at work. It seems to me that chiefly MySQL is at fault here if it is indeed throwing an error and yet still writing it to the db. It seems that log4j could solve this by changing the execute() method to be in charge of adding to the removes.add(..) call, and then having a setAutoCommit in there so that a rollback is performed if an Exception is thrown (and the removes.add(...) is not done). This change of responsibility might be bad for subclasses; so the other option would be to change execute() to take a Connection parameter and put flushBuffer() in charge of the Connection. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
