Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user-java@ibatis.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-Id: <EB41B206-10F6-4743-B314-BE57183BE92D@ezabel.com>
From: Ian Zabel <ian@ezabel.com>
To: user-java@ibatis.apache.org
In-Reply-To: <48A2073E.1060801@earthlink.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v926)
Subject: Re: Really Weird Oracle REF Cursor Behavior
Date: Tue, 12 Aug 2008 22:36:15 -0400
References: <e38beafa0808121441r5eb5c1di2860e57d3a9d2197@mail.gmail.com>
 <48A2073E.1060801@earthlink.net>

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 here we've found that  
> stored functions (where the Cursor is returned from the function and  
> not fetched into an out parameter) works best.
>
> Hope This Helps,
>
> Jeff Stahl
>
> Ian Zabel wrote:
>> 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 in that column, ROW 1 does _not_ return in the
>> ResultSet from the REF Cursor when using iBATIS.
>> ROW 1: mts - Sample Invoice, b2325
>> ROW 2: mts - New Invoice, b2330
>>
>> However, if we update the column in ROW 1 with the value from ROW 2,
>> then the row returns fine.
>>
>> Also, when using straight JDBC, the rows are returned.
>>
>> I've tried disabling cacheModels, enhancement, and lazyLoading, to no
>> avail. When debugging into the iBATIS
>> SqlExecutor.retrieveOutputParameters method, the ResultSet that it
>> gets on line 399 does not include the row. In fact, if this row is  
>> the
>> only row returned by the query, the ResultSet has no results at all.
>>
>> Any ideas? I'm really confused because it works fine with JDBC using
>> the same connection as iBATIS, and if we change the data somewhat,
>> then it returns fine.
>>
>> Thanks,
>> Ian.
>>
>>
>>