Did you re-build DBD-Oracle after you installed the new Oracle? Sometimes
you can get away with sticking with the old build, but not always.
Doing something with blob_read() is on the Todo list, but it doesn't look
like much has been done with it in a long time. The OCI8 version of
DBD::Oracle only works with CLOBs and BLOBs at last report.
For now it's undocumented and experimental. If you need it, a patch to Tim
that at least documents it (in DBI) and preferably adds LONGs to the OCI8
version (in DBD::Oracle) would probably push it over the top.
--
Mac :})
** I normally forward private database questions to the DBI mail lists. **
Give a hobbit a fish and he'll eat fish for a day.
Give a hobbit a ring and he'll eat fish for an age.
----- Original Message -----
From: "Gilad Tsur" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "Gilad Tsur" <[EMAIL PROTECTED]>
Sent: Sunday, March 25, 2001 7:08 AM
Subject: DBD::Oracle won't Clob with 8.1.7 client
> I'm running DBD1.06 on a Linux machine. All worked well as long as we used
> Oracle client 8.1.5. Once we made the change to 8.17, we failed to read
> CLOB's continuously. An example script with output for 8.15 and 8.1.7
> follow:
> . . .
> results on Oracle 8.1.7 are:
>
> Starting Length=10200
> --Step 1 done --
> database now open
> DBD::Oracle::st fetchrow_array failed: (DBD NEED_DATA: OCILobRead) at
> ./testClob2.pl line 41.
> Issuing rollback() for database handle being DESTROY'd without explicit
> disconnect().
>
>
> results on Oracle 8.1.5:
>
> Starting Length=10200
> --Step 1 done --
> database now open
> 3: CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC (... around 10200 'C's)
>
> Similar results follow when using regular fetchrow_hashref and such,
without
> blob_read.
> Any advice?
> While I'm at it, is blob_read the "new" standard, or is it slowly becoming
> deprecated? Is it well documented somewhere?
