Thanks for closing the loop. It's nice to not have potential sporadic
behavior.
On Fri, Aug 22, 2008 at 1:35 PM, Ian Zabel <[EMAIL PROTECTED]> wrote:
> I finally got back to look at this, and discovered the problem.
>
> One of the s in the was defined in the xml
> as the incorrect JDBC and Java
I finally got back to look at this, and discovered the problem.
One of the s in the was defined in the xml
as the incorrect JDBC and Java type.
It was:
When it should have been:
Since the stored proc was actually doing some char operations on that
input parameter, this seemed to have been sc
I haven't had a chance to test the 2.3.x release. Has the problem with
Oracle ref cursors been fixed then? It's not that we couldn't move
forward (we discovered that stored functions work just fine nearly a
year ago, and that's our standard approach); in fact we have 6 projects
using the same
It shouldn't... :-/
Can you provide a failing test case?
On Tue, Aug 12, 2008 at 3:57 PM, Jeff Stahl <[EMAIL PROTECTED]> wrote:
> iBATIS seems to have a problem with handling RefCursors as OUT parameters
> in stored procedures. I don't know how you're attempting to use iBATIS in
> your project,
Very interesting. How do you map something like that?
Thanks,
Ian.
On Aug 12, 2008, at 5:57 PM, Jeff Stahl wrote:
iBATIS seems to have a problem with handling RefCursors as OUT
parameters in stored procedures. I don't know how you're attempting
to use iBATIS in your project, but in house h
Could you send your Ibatis configs. I am having data like those successfully
processed.
On Tue, Aug 12, 2008 at 2:57 PM, Jeff Stahl <[EMAIL PROTECTED]> wrote:
> iBATIS seems to have a problem with handling RefCursors as OUT parameters
> in stored procedures. I don't know how you're attempting to
iBATIS seems to have a problem with handling RefCursors as OUT
parameters in stored procedures. I don't know how you're attempting to
use iBATIS in your project, but in house here we've found that stored
functions (where the Cursor is returned from the function and not
fetched into an out para
Hello,
Using the latest build of iBATIS and Oracle REF Cursors, we're running
into a problem with certain rows not coming back in the ResultSet. It
seems to be certain data in the rows that makes them not return.
For example, we have a column called INTERNAL_INVOICE_NBR. With the
following values
