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

From: lembark@xxxxxxxxxxx (Steven Lembark)
Date: Wed, 13 Jul 2005 13:44:09 -0400

-- "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.


That's what I'm trying to avoid. The problem is that
doing so requires pre-checking every incomming SQL
to see if there is a CLOB in it. If there were some
internal Oracle function for "insert the following
string as a CLOB" then I could avoid the issue in
the SQL rather than dealing with it in the closure.


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

References:
- RE: DBI-1.48 bind_param_inout produces ORA-01461 colliding with a CLOB
  - From: Ron Reidy

Prev by Date: RE: selectall_hashref() when key field not unique
Next by Date: RE: selectall_hashref() when key field not unique
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):
- Date
- Thread