apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Darroch <chr...@pearsoncmg.com>
Subject Re: DBD: Prepared statements, BLOBs etc.
Date Thu, 18 Jan 2007 04:44:29 GMT
Hi --

Bojan Smojver wrote:

> Looks pretty simple, doesn't it? Well, I tried with Oracle XE
> client and Instant Client, all connecting to Oracle XE Server
> (Universal and not) on Linux - no go. I get:
> Execute error -1: ORA-01461: can bind a LONG value only for insert into
> a LONG column

   You could be hitting a character set conversion issue between
your client and the server, or simply a poor piece of Oracle documentation.
A few possibilities are mentioned here:


They talk about "ML" or MetaLink in that thread; that's the central
Oracle support site.  Several "notes" from MetaLink are partially quoted.

> Now, the strange thing is that the size of BLOB and CLOB in my table is
> reported as 4000 bytes. Aren't these things supposed to hold at least
> gigabytes?

   Yes, they should.  But, the documentation makes fairly clear that
a 4 KB limit is imposed on a lot of internal conversions and
operations.  If you can get it working, more power to you!  You
asked elsewhere about the murky subject of Oracle character sets and
I'm afraid I'm far from expert on it.

   Personally I'm beginning to wonder if it wouldn't make more sense
to effectively return APR_ENOTIMPL and only provide LOB handling for
"sane" DB servers.  Maybe a driver-specific set of calls could provide
special handling for those that really needed it.


GPG Key ID: 366A375B
GPG Key Fingerprint: 485E 5041 17E1 E2BB C263  E4DE C8E3 FA36 366A 375B

View raw message