t/base..............ok
t/general...........ok
t/long..............ok 36/143LONG RAW: ORA-02005: implicit (-1) length not
valid for this bind or define datatype (DBD ERROR: OCIBindByName) at
t/long.t line 131.
t/long..............dubious
Test returned status 255 (wstat 65280, 0xff00)
DIED. FAILED tests 37-143
Failed 107/143 tests, 25.17% okay
Verbose version:
t/long..............
:
:
ok 33
ok 34
ok 35
long_data0 length 20480
long_data1 length 81920
long_data2 length 71680
create table dbd_ora__drop_me ( idx integer, lng LONG RAW, dt date )
--- insert some LONG RAW data
ok 36
LONG RAW: ORA-02005: implicit (-1) length not valid for this bind or define
datatype (DBD ERROR: OCIBindByName) at t/long.t line 131.
dubious
Test returned status 255 (wstat 65280, 0xff00)
DIED. FAILED tests 37-143
Failed 107/143 tests, 25.17% okay
>From looking through the archives it appears that this only happens if perl
is built with 64-bit integer support, and it is probably caused by the
common 'passing 64 bit int where 32 bit int was expected' problem, usually
curable by a quick cast or two. In this case it looks like the length
parameter is incorrect. However, I'm not familiar enough with the
DBI::Oracle source to know where to start looking - can someone point me in
the vicinity of the code that is responsible for inserting LONG RAWs?
Thanks,
--
Alan Burlison
--
$ head -1 /dev/bollocks
generate unconstrained action items
