Re: IBATIS support for postgres cursors

Hi Guy,

Thanks for your reply. We were able to work out with type OTHER.

Many thanks for support.

Regards,
Atul Goel

-----Original Message-----
From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Guy Rouillier
Sent: 25 August 2010 08:03
To: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] IBATIS support for postgres cursors

On 8/23/2010 12:11 PM, Atul(dot)Goel(at)globaldatapoint(dot)com wrote:
> Hi,
>
> Can cursors be returned to IBATIS. If so how. This is what I have written.
>
> <parameterMap id=/"/ /getUsersParam"/ class=/"Map"/>
>
> <parameter property=/"results"/ jdbcType=/"REF"/
> javaType=/"java.sql.ResultSet"/ mode=/"OUT"/ resultMap=/"allUsersResult"//>
>
> <parameter property=/"errors"/ jdbcType=/"VARCHAR"/
> javaType=/"java.lang.String"/ mode=/"OUT"//>
>
> </parameterMap>
>
> This does not work. Please help.

There is a dedicated mailing list for MyBatis (renamed from iBATIS) over
at http://www.mybatis.org. This question would probably be better
addressed there. I use both PG and MyBatis so I saw your question. REF
is not an acceptable MyBatis jdbcType. I'm trying with type OTHER as
documented here:

http://jdbc.postgresql.org/documentation/83/callproc.html#callproc-resultset-setof

But I'm running into an issue which I'll pursue on the MyBatis mailing
list. Note that with the current refcursor implementation, there is no
advantage over returning SETOF from your function. Both materialize the
entire result set before returning to the caller. So, if you can't get
refcursor to work, I'd suggest switching to SETOF.

I'll get back to you when I find out why OTHER is not working. Or else
you can join the MyBatis mailing list.

--
Guy Rouillier

--
Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
This e-mail is confidential and should not be used by anyone who is not the original intended recipient. Global DataPoint Limited does not accept liability for any statements made which are clearly the sender's own and not expressly made on behalf of Global DataPoint Limited. No contracts may be concluded on behalf of Global DataPoint Limited by means of e-mail communication. Global DataPoint Limited Registered in England and Wales with registered number 3739752 Registered Office Middlesex House, 34-42 Cleveland Street, London W1T 4LB