In the generated save method, if an error occurs, BasePeer.rollBackTransaction is called. However, if an error occurs in the rollBackTransaction, the user loses anything about the original error and only sees the rollBackEx.
I've attached two patches: torque-rollback-save.txt -- Ignores the rollBackEx and just returns the original exception from save torque-rollback-save-notify.txt -- Returns a new TorqueException with the text of the original save exception appended with the text of the rollBackEx so that the user at least knows the rollBackEx occurred. I personally like the first patch, but if rollBackEx are a big deal and somehow reflect an error in the database, then the second patch would be more appropriate. - Stephen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
