On 05-Sep-2006 Martin J. Evans wrote: > > On 05-Sep-2006 Tim Bunce wrote: >> On Tue, Sep 05, 2006 at 11:20:04AM +0100, Martin J. Evans wrote: >>> >>> I'll report the problems just as soon as I'm certain what they are. Here is >>> my summary: >>> >>> 1. insert into table values (?,?) where all values are valid and 3 rows of >>> values >>> >>> returns: 3 >>> (correct as 3 tuples executed) >>> ArrayTupleStatus = (-1, -1, -1) >>> (incorrect - should be (1,1,1) as DBD::Oracle does know a row was >>> inserted each time as evidenced by execute itself which returns >>> rows >>> affected) >>> >>> 2. insert into table values (?,?) where there are 2 rows of data but second >>> one >>> is invalid >>> >>> returns: undef >>> (correct) >>> ArrayTupleStatus = (-1, [1772, 'ORA-01722.......']) >>> (incorrect as this should be (1, [1772, 'ORA-01722.......']) >>> probably same issue as 1). >>> >>> 3. update table where the update does not affect any rows >>> >>> returns: 0 >>> (incorrect - should be 1 for 1 tuple executed) >>> ArrayTupleStatus = (-1) >>> (incorrect - should be (0) for no rows affected) >>> >>> If my conclusions look right to you I'll report them on rt. >> >> You're spot on. > > OK, will report these issue this afternoon. >
Reported at http://rt.cpan.org/Ticket/Display.html?id=21331 <snipped aside> Martin -- Martin J. Evans Easysoft Ltd, UK http://www.easysoft.com
