Re: DBD::Oracle 11gr2 ORA-38909

2010-06-04 Thread John Scoles
Had a quick look at it today give it a try agian but this time make sure you have autocommit off AutoCommit=1 on the connection method cheers On Fri, May 21, 2010 at 11:20 AM, John Scoles sco...@pythian.com wrote: Ok I guess it is back to square 1 on this. Unfortunetly no time to look at

Re: DBD::Oracle 11gr2 ORA-38909

2010-05-21 Thread Martin Evans
John Scoles wrote: Ok I have patched up a solution I think will work across the board and you can find it here http://svn.perl.org/modules/dbd-oracle/branches/oci_batch here are the details ora_oci_batch For 11g users you may encounter an error while using the execute_array in that

Re: DBD::Oracle 11gr2 ORA-38909

2010-05-21 Thread Scott T. Hildreth
On Fri, 2010-05-21 at 09:23 +0100, Martin Evans wrote: John Scoles wrote: Ok I have patched up a solution I think will work across the board and you can find it here http://svn.perl.org/modules/dbd-oracle/branches/oci_batch here are the details ora_oci_batch For 11g users

Re: DBD::Oracle 11gr2 ORA-38909

2010-05-21 Thread John Scoles
Ok I guess it is back to square 1 on this. Unfortunetly no time to look at it today Will write up a small test script and see if my patch actually does anything You may hear from me in a few days Cheers John Scott T. Hildreth wrote: On Fri, 2010-05-21 at 09:23 +0100, Martin Evans wrote:

Re: Clarification sought on private_attribute_info WAS Re: DBD::Oracle 11gr2 ORA-38909

2010-05-10 Thread Tim Bunce
[Sorry for the delay] On the one hand, the DBI makes a distinction between method attributes and handle attributes. They're different things. On the other hand, the handle constructor methods are a special case. The method attributes passed to connect() are applied to the newly created dbh as

Re: DBD::Oracle 11gr2 ORA-38909

2010-05-07 Thread John Scoles
On Tue, Apr 6, 2010 at 4:51 AM, Martin Evans martin.ev...@easysoft.comwrote: I haven't seen a reply to this yet but I've been on holiday so might have missed it: Scott T. Hildreth wrote: On Wed, 2010-03-31 at 12:20 -0500, Scott T. Hildreth wrote: We have run into an issue with array

Clarification sought on private_attribute_info WAS Re: DBD::Oracle 11gr2 ORA-38909

2010-05-07 Thread Martin Evans
Apologies for top posting but this is an old thread and I include it for reference but really I'd like some clarification from Tim as to whether the following is correct. As John states the DBI documentation says for private_attribute_info: Returns a reference to a hash whose keys are the names

Re: DBD::Oracle 11gr2 ORA-38909

2010-05-07 Thread John Scoles
Ok I have patched up a solution I think will work across the board and you can find it here http://svn.perl.org/modules/dbd-oracle/branches/oci_batch here are the details ora_oci_batch For 11g users you may encounter an error while using the execute_array in that it does not return a full list

Re: DBD::Oracle 11gr2 ORA-38909

2010-04-06 Thread Martin Evans
I haven't seen a reply to this yet but I've been on holiday so might have missed it: Scott T. Hildreth wrote: On Wed, 2010-03-31 at 12:20 -0500, Scott T. Hildreth wrote: We have run into an issue with array processing in 11g. The developer was using execute_array and his sql statement had

Re: DBD::Oracle 11gr2 ORA-38909

2010-04-06 Thread Scott T. Hildreth
On Tue, 2010-04-06 at 09:51 +0100, Martin Evans wrote: I haven't seen a reply to this yet but I've been on holiday so might have missed it: Scott T. Hildreth wrote: On Wed, 2010-03-31 at 12:20 -0500, Scott T. Hildreth wrote: We have run into an issue with array processing in 11g. The

Re: DBD::Oracle 11gr2 ORA-38909

2010-04-02 Thread Scott T. Hildreth
On Wed, 2010-03-31 at 12:20 -0500, Scott T. Hildreth wrote: We have run into an issue with array processing in 11g. The developer was using execute_array and his sql statement had 'LOG ERRORS' in it. This did not error out until we switched to 11g. The issue is that only one is allowed,

DBD::Oracle 11gr2 ORA-38909

2010-03-31 Thread Scott T. Hildreth
We have run into an issue with array processing in 11g. The developer was using execute_array and his sql statement had 'LOG ERRORS' in it. This did not error out until we switched to 11g. The issue is that only one is allowed, either 'LOG ERRORS' or 'SAVE EXCEPTIONS'. Our DBA logged and error