> Date: Wed, 11 Feb 2009 12:38:15 +0000> From: [email protected]> To:
> [email protected]> CC: [email protected]> Subject: Re: Issue with
> bind_param_inout and sys_refcursor> > On 10/02/09 19:48, snutr wrote:> >
> Hello,> > > > I'm having an issue with getting a sys_refcursor back from a
> function.> > [snip]> > > It fails and produces the following output:> > > > >
> > Field 9 has an Oracle type (108) which is not explicitly supported> > at
> ./test4_ora.pl line 23.> > Field 18 has an Oracle type (108) which is not
> explicitly supported> > at ./test4_ora.pl line 23.> > Field 19 has an Oracle
> type (108) which is not explicitly supported> > at ./test4_ora.pl line 23.> >
> Field 20 has an Oracle type (108) which is not explicitly supported> > at
> ./test4_ora.pl line 23.> > DBD::Oracle::st execute failed: ERROR
> OCIDefineObject call needed but> > not implemented yet [for Statement
> "declare csr sys_refcursor;> > begin :csr := my_function('12345','','');
> end;" with> > ParamValues: :csr=DBI::st=HASH(0x33180c)] at ./test4_ora.pl
> line 23.> > I think this is trying to tell you that DBD::Oracle cannot cope>
> with some of the columns in the actual cursor returned. Specifically,> it is
> telling you that the types of the 9th, 18th, 19th and 20th columns> are
> user-defined Object types. DBD::Oracle does not support these types.>
Well that is only half true.
DBD::Oracle after 1.20 will handle them and retrun them an arrays of scalars.
> -- > Charles Jardine - Computing Service, University of Cambridge>
> [email protected] Tel: +44 1223 334506, Fax: +44 1223 334679
_________________________________________________________________
Twice the fun—Share photos while you chat with Windows Live Messenger.
http://www.microsoft.com/windows/windowslive/products/messenger.aspx
