Re: DBI-1.48 bind_param_inout produces ORA-01461 colliding with a CLOB
- From: hjp@xxxxxxxxx (Peter J. Holzer)
- Date: Wed, 20 Jul 2005 10:59:25 +0200
On 2005-07-13 13:00:28 -0400, Steven Lembark wrote:
> The code that blows up is a generic query handler.
> The code here returns a closure bound for a
> specific query. In this case, for an
> insert ... returning query:
>
> ...
>
> my @bound = ( 1..$total );
>
> my @copy = ( 0..$countz{insert}-1 );
> my @return = ( $countz{insert} .. $#bound );
>
> $sth->bind_param_inout( $_+1, \$bound[$_], 4096 )
> for( 0 .. $#bound );
How generic has does the query handler have to be? Can you get rid of
the bind_param_inout? If you don't bind the parameters explicitely and
just pass them as parameters to execute, DBD::Oracle will perform the
necessary magic for you.
hp
--
_ | Peter J. Holzer \Beta means "we're down to fixing misspelled comments in
|_|_) | Sysadmin WSR \the source, and you might run into a memory leak if
| | | hjp@xxxxxxxxx \you enable embedded haskell as a loadable module and
__/ | http://www.hjp.at/ \write your plugins upside-down in lisp". --ae@xxxxxx
Attachment:pgp7SwuEmqMHn.pgp
Description: PGP signature
- References:
- DBI-1.48 bind_param_inout produces ORA-01461 colliding with a CLOB
- From: Steven Lembark
- DBI-1.48 bind_param_inout produces ORA-01461 colliding with a CLOB
- Prev by Date: Re: DBD::Informix Build Error On 64bit AIX 5.2
- Next by Date: Re: Sorting on a partial email address
- Previous by thread: Re: DBI-1.48 bind_param_inout produces ORA-01461 colliding with a CLOB
- Next by thread: RE: DBI-1.48 bind_param_inout produces ORA-01461 colliding with a CLOB
- Index(es):
Relevant Pages
|
