[Mono-bugs] [Bug 78898][Maj] New - OracleClient Lob handling is different in MS.Net

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by skolima at gmail.com.

http://bugzilla.ximian.com/show_bug.cgi?id=78898

--- shadow/78898	2006-07-19 07:58:06.000000000 -0400
+++ shadow/78898.tmp.7242	2006-07-19 07:58:06.000000000 -0400
@@ -0,0 +1,55 @@
+Bug#: 78898
+Product: Mono: Class Libraries
+Version: 1.1
+OS: All
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: Sys.Data
+AssignedTo: tsenganal at novell.com                            
+ReportedBy: skolima at gmail.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Summary: OracleClient Lob handling is different in MS.Net
+
+Description of Problem:
+
+In MS.Net, LOB's position is a 0-based index. In mono, the index starts
+with 1, as in OCI. This breaks aplications that try to seek in the stream
+provided by LOB. Fixing this will require changes in test's, as they rely
+on this (wrong) behaviour.
+
+
+Steps to reproduce the problem:
+1. Create a LOB in oracle database
+2. Read it :
+
+OracleConnection dbcon = new OracleConnection (connectionString);
+		dbcon.Open();
+       
+		OracleCommand dbcmd = dbcon.CreateCommand ();
+		string sql = ""; // select the lob
+		dbcmd.CommandText = sql;
+		OracleDataReader reader = dbcmd.ExecuteReader ();
+		if (reader.Read ()) {
+			OracleLob st = reader.GetOracleLob(1);
+                        //st.Seek(0, SeekOrigin.Begin);
+			Console.WriteLine ("position: " + st.Position);
+
+
+Actual Results:
+1
+
+Expected Results:
+0
+
+Also, a Seek to 0 will cause the subsequent reads to throw exceptions,
+while they shoul succeed.
+
+How often does this happen? 
+Always.
+
+Additional Information: