[svn:dbd-oracle] r15332 - in dbd-oracle/trunk: . lib/DBD/Oracle

Author: mjevans
Date: Sun Jun 24 02:07:10 2012
New Revision: 15332

Modified:
   dbd-oracle/trunk/Changes
   dbd-oracle/trunk/lib/DBD/Oracle/Troubleshooting.pm

Log:
rt71819 - troubleshoiting entry for bound output parameters returned in wrong order


Modified: dbd-oracle/trunk/Changes
==============================================================================
--- dbd-oracle/trunk/Changes	(original)
+++ dbd-oracle/trunk/Changes	Sun Jun 24 02:07:10 2012
@@ -1,5 +1,12 @@
 Revision history for DBD::Oracle
 
+1.NN next release
+
+  [MISCELLANEOUS]
+
+  - Added a trouble shooting entry for RT71819 - bound output
+    parameters may be returned in the wrong order.
+
 1.45_00   2012-06-21
 
  [CHANGE IN BEHAVIOUR]

Modified: dbd-oracle/trunk/lib/DBD/Oracle/Troubleshooting.pm
==============================================================================
--- dbd-oracle/trunk/lib/DBD/Oracle/Troubleshooting.pm	(original)
+++ dbd-oracle/trunk/lib/DBD/Oracle/Troubleshooting.pm	Sun Jun 24 02:07:10 2012
@@ -375,6 +375,17 @@
 
 It looks like this was fixed in 0.012 of Module::Runtime.
 
+=head2 bin_param_inout spapping return values
+
+See RT 71819 (https://rt.cpan.org/Ticket/Display.html?id=71819)
+
+It seems that in some older versions of Oracle Instant Client
+(certainly 10.2.0.4.0) when output parameters are bound with lengths
+greater than 3584 the output parameters can be returned in the wrong
+placeholders.
+
+It is reported fixed in Instant Client 11.2.0.2.0.
+
 =head1 AUTHORS
 
 =over 4