RE: DBI-1.48 bind_param_inout produces ORA-01461 colliding with a CLOB



Well, I am not sure how we can change the Oracle way of doing this and I know of no DB functions that will or could perform this task easily.

Maybe you will need to sub class DBD::Oracle and create your own methods for handling LOBs to allow for this transparency

-----------------
Ron Reidy
Lead DBA
Array BioPharma, Inc.


-----Original Message-----
From: Steven Lembark [mailto:lembark@xxxxxxxxxxx]
Sent: Wednesday, July 13, 2005 12:24 PM
To: Reidy, Ron; dbi-users@xxxxxxxx
Subject: RE: DBI-1.48 bind_param_inout produces ORA-01461 colliding with
a CLOB




-- "Reidy, Ron" <Ron.Reidy@xxxxxxxxxxxxxxxxxx>

> Steve,
>
> See the DBD::Oracle docs, section "Handling LOBs". Basically, you need to
> insert a EMPTY_CLOB(), return the locator, and then call ora_write_lob()
> to push the data into the locator.

This is a generic query handler. In order to do that I have to
investigate the data type of each '?' in the input sql, determine
if it is a LOB, and handle that field specially. If there were
something like convert for a clob then I could push the knowlege
of clob-ness up into the SQL.

This code is also used for other databases (e.g., MySQL, which
handles text fields more gracefully).

--
Steven Lembark 85-09 90th Street
Workhorse Computing Woodhaven, NY 11421
lembark@xxxxxxxxxxx 1 888 359 3508

This electronic message transmission is a PRIVATE communication which contains
information which may be confidential or privileged. The information is intended
to be for the use of the individual or entity named above. If you are not the
intended recipient, please be aware that any disclosure, copying, distribution
or use of the contents of this information is prohibited. Please notify the
sender of the delivery error by replying to this message, or notify us by
telephone (877-633-2436, ext. 0), and then delete it from your system.

.



Relevant Pages

  • Res: RE: RE: Problems changing from 1.30 to 1.42
    ... With DBI 1.30 it works just it is: ... >>This electronic message transmission is a PRIVATE communication which contains ... >>intended recipient, please be aware that any disclosure, copying, distribution ... >>sender of the delivery error by replying to this message, or notify us by ...
    (perl.dbi.users)
  • RE: RE: Problems changing from 1.30 to 1.42
    ... >This electronic message transmission is a PRIVATE communication which contains ... >intended recipient, please be aware that any disclosure, copying, distribution ... >sender of the delivery error by replying to this message, or notify us by ...
    (perl.dbi.users)
  • RE: RE: DBI->Connect returning UNDEF in cgi but not in standalone prog
    ... You are returning undef. ... >This electronic message transmission is a PRIVATE communication which contains ... >intended recipient, please be aware that any disclosure, copying, distribution ... >sender of the delivery error by replying to this message, or notify us by ...
    (perl.dbi.users)
  • RE: RE: Problems changing from 1.30 to 1.42
    ... >This electronic message transmission is a PRIVATE communication which contains ... >intended recipient, please be aware that any disclosure, copying, distribution ... >sender of the delivery error by replying to this message, or notify us by ...
    (perl.dbi.users)
  • RE: make problem
    ... Perl may be copied only under the terms of either the Artistic License or the ... This electronic message transmission is a PRIVATE communication which contains information ... If you are not the intended recipient, please be aware that any disclosure, ... Please notify the sender ...
    (perl.dbi.users)