Unfortunately not at this time. But I wonder if we could add support for a connection lifecycle event handler. So that when a connection is retrieved from the datasouce, you have an opportunity to manipulate it and set such properties -- without having to resort to user supplied connections all the time.
Would that work?
Thoughts?
Clinton
On 9/13/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
I have a problem with the way that Sybase ASE works with stored procs and triggers. I'm working with a legacy database that is very poorly designed. All work is performed using procs and triggers and it's almost impossible to trace it all down. The problem I'm having is that ASE build results sets, know as done-in-proc result sets, for each proc that is executed. As most of the triggers on this databases tables call sp's there can be a large number of done-in-proc resultSets.The problem manifests itself when an error is raised by a proc. The execution of the SQL Statement returns but there can be multiple result sets and only the last one contains the error. The JConnect JDBC driver has a parameter that can be set, (IGNORE_DONE_IN_PROC) that tells the driver to ignore the done-in-proc result sets and only look at the last one. (NO brainner right?)My question is, is there a way to tell iBatis to only look at the last result set so I don't need to set the parameter on the connection? I know support for multiple result sets was recently added but I don't think that it was intended to be used for this type of situation.Thanks....
