r56743 - /trunk/libdbd-oracle-perl/debian/patches/01_Fix_Podman_Errors

[jump-guest at users.alioth.debian.org]

Author: jump-guest
Date: Sat Apr 24 06:25:17 2010
New Revision: 56743

URL: http://svn.debian.org/wsvn/pkg-perl/?sc=1&rev=56743
Log:
Patch to Fix Podman Errors

Added:
    trunk/libdbd-oracle-perl/debian/patches/01_Fix_Podman_Errors

Added: trunk/libdbd-oracle-perl/debian/patches/01_Fix_Podman_Errors
URL: http://svn.debian.org/wsvn/pkg-perl/trunk/libdbd-oracle-perl/debian/patches/01_Fix_Podman_Errors?rev=56743&op=file
==============================================================================
--- trunk/libdbd-oracle-perl/debian/patches/01_Fix_Podman_Errors (added)
+++ trunk/libdbd-oracle-perl/debian/patches/01_Fix_Podman_Errors Sat Apr 24 06:25:17 2010
@@ -1,0 +1,108 @@
+Description: Fix podman errors.
+Author: Julián Moreno Patiño <darkjunix at gmail.com
+Index: libdbd-oracle-perl/Oracle.pm
+===================================================================
+--- libdbd-oracle-perl.orig/Oracle.pm	2010-04-23 19:24:08.570380081 -0500
++++ libdbd-oracle-perl/Oracle.pm	2010-04-23 20:04:32.266398924 -0500
+@@ -1468,6 +1468,7 @@
+ 
+   OCI_STMT_SCROLLABLE_READONLY 
+ 
++=back
+ 
+ =head1 Attributes
+ 
+@@ -1871,6 +1872,8 @@
+ Specify internal data representation. Currently is supported only for
+ ORA_NUMBER_TABLE.
+ 
++=back
++
+ =head1 Optimizing Results
+ 
+ =head2 Prepare postponed till execute
+@@ -1939,8 +1942,6 @@
+ number of rows to prefetch otherwise the number of rows will be limited to memory size. Likewise if the RowCacheSize is less than 1 it
+ is not included in the computing of the prefetch rows.  
+ 
+-=back
+-
+ =head1 Spaces & Padding
+ 
+ =head2 Trailing Spaces
+@@ -2853,8 +2854,12 @@
+ 
+ 3 = Both character sets are Unicode encodings.
+ 
++=back
++
+ =head1 Private statement handle functions
+ 
++=over
++
+ =item ora_stmt_type
+ 
+ Returns the OCI Statement Type number for the SQL of a statement handle.
+@@ -2904,6 +2909,8 @@
+ 
+ The following driver-specific methods are used with scrollable cursors.
+ 
++=over
++
+ =item ora_scroll_position
+ 
+   $position =  $sth->ora_scroll_position();
+@@ -2965,6 +2972,8 @@
+   OCI_FETCH_RELATIVE, and a fetch offset value that is less than 1 is equivalent to a OCI_FETCH_CURRENT.
+   OCI_FETCH_RELATIVE, and a fetch offset value that makes it greater than the number of records in the record set, is equivalent to a OCI_FETCH_CURRENT.
+ 
++=back
++
+ =head2 Scrollable Cursor Usage
+ 
+ Given a simple code like this:
+@@ -2983,6 +2992,8 @@
+ and one assumes that the number of rows returned from the query is 20, the code snippets below will illustrate the use of ora_fetch_scroll
+ method;
+ 
++=over
++
+ =item Fetching the Last Row
+ 
+   $value =  $sth->ora_fetch_scroll(OCI_FETCH_LAST,0);
+@@ -3079,6 +3090,8 @@
+ When using scrollable cursors it is required that you use the $sth->finish() method when you are done with the cursor as this type of
+ cursor has to be explicitly canceled on the server. If you do not do this you may cause resource problems on your database.  
+ 
++=back
++
+ =head1 LOBs and LONGs
+ 
+ The key to working with LOBs (CLOB, BLOBs) is to remember the value of an Oracle LOB column is not the content of the LOB. It's a
+@@ -3088,6 +3101,8 @@
+ 
+ DBD::Oracle now offers three interfaces to LOB and LONG data, 
+ 
++=over
++
+ =item L</Data Interface for Persistent LOBs>
+ 
+ With this interface DBD::Oracle handles your data directly utilizing regular OCI calls, Oracle itself takes care of the LOB Locator operations in the case of 
+@@ -3108,6 +3123,8 @@
+ 
+ One point to remember when working with LOBs (CLOBs, BLOBs) is if your LOB column can be in one of three states;
+ 
++=over
++
+ =item NULL
+ 
+ The table cell is created, but the cell holds no locator or value.
+@@ -3131,6 +3148,8 @@
+ 
+ A LOB instance with a locator and a value exists in the cell. You actually get the LOB value.
+ 
++=back
++
+ =head2 Data Interface for Persistent LOBs
+ 
+ This is the original interface for LONG and LONG RAW datatypes and from Oracle 9iR1 and later the OCI API was extended to work directly with the other LOB datatypes.