PROTECTED]
Subject: Re: Oracle ref cursors
Hmmm...ok. Here's what I'd like to see in a solution:
* No dependency upon Oracle (like you've said).
* ResultSet types should be supported in both OUT parameters, as well as
result set columns (ick).
* The regular result se
Hmmm...ok. Here's what I'd like to see in a solution: * No dependency upon Oracle (like you've said). * ResultSet types should be supported in both OUT parameters, as well as result set columns (ick).
* The regular result set returned by a select statement or procedure should not be compromise
Yep. I agree on the need. Just being cautious about the implementation.Cheers,ClintonOn 2/9/06, Sven Boden <
[EMAIL PROTECTED]> wrote:In case anyone is interested in having a look, I uploaded the "patch to
the patch" to the wiki,http://opensource2.atlassian.com/confluence/oss/display/IBATIS/Oracl
In case anyone is interested in having a look, I uploaded the "patch to
the patch" to the wiki,
http://opensource2.atlassian.com/confluence/oss/display/IBATIS/Oracle+REF+CURSOR+Solutions
We may need to think some other things over, but a lot of people seem to
need/want something in iBATIS
There can be more than 1 out result sets, Michael's testcases on the
wiki show that.
Will check the second bullet tomorrow, we can probably find a way around
it it should also be just a resultset (but I vaguely remember some
problems with it from past experiments).
Sven
Clinton Begin
So the assumptions made here are: * There can be only one out parameter of type ResultSet * The default result set (possibly returned from a SELECT) is lost, as it's overidden by the ResultSet parameter.
Seems a bit hackey, but I'm interested in everyone else's opinion. ClintonOn 2/9/06, Sven Bo
