[Mono-bugs] [Bug 67269][Nor] New - returning 1000 row dataset fails with apparent success

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 30 Sep 2004 18:12:42 -0400 (EDT)


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 stm3@qwest.net.

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

--- shadow/67269	2004-09-30 18:12:42.000000000 -0400
+++ shadow/67269.tmp.10123	2004-09-30 18:12:42.000000000 -0400
@@ -0,0 +1,89 @@
+Bug#: 67269
+Product: Mono: Runtime
+Version: unspecified
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: stm3@qwest.net               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: returning 1000 row dataset fails with apparent success
+
+XSP RUNTIME MONO 1.01 WINDOWS
+
+Description of Problem:
+1000 row dataset converted to XML is truncated into a 0 row dataset 
+containing only the table schema:
+
+Steps to reproduce the problem:
+In a webmethod, load 1000 row recordset into dataset (I used the ORDERS 
+table from the NORTHWIND sample db.  Convert to XML.  XML conversion 
+fails, but with no error, and generates a 0 record dataset with only the 
+schema, as if no records matched the query.  Return string to client.  XSP 
+terminates immediately after exiting WebMethod.
+Some of the ORDER records below may not be in the sample database.  I 
+populated it with a 100,000 records beyond what it already had, but I 
+believe that table has well over 1000 records in it to begin with (3 
+dates, 2 floats, 5 or 6 ints, 15 or so fixed-length strings)
+
+		[WebMethod]
+		public string returnRecordset ()
+		{
+			try
+			{
+				System.Data.Odbc.OdbcConnection conn = new 
+System.Data.Odbc.OdbcConnection();
+				conn.ConnectionString = "DSN=NorthWind";
+				conn.Open();
+				System.Data.Odbc.OdbcCommand command = new 
+System.Data.Odbc.OdbcCommand
+					("SELECT * FROM ORDERS where 
+OrderId > 100001 and OrderId < 101000", conn);
+				System.Data.Odbc.OdbcDataAdapter da = new 
+System.Data.Odbc.OdbcDataAdapter();
+				da.SelectCommand = command;
+				System.Data.DataSet ds = new DataSet
+("Orders");
+				da.Fill (ds);
+				System.IO.StringWriter tw = new 
+System.IO.StringWriter();
+				ds.WriteXml(tw, 
+System.Data.XmlWriteMode.WriteSchema);
+				conn.Close();
+				return tw.ToString();
+			}
+			catch(System.Exception se)
+			{
+				return se.Message;
+			}
+			
+
+		}
+2. 
+3. 
+
+Actual Results:
+0 row table returned to client.  XSP web server terminates itself.
+Client will assume a success with no matching records.
+
+Expected Results:
+exception thrown to client or better yet, success.  (ASP.NET handled up to 
+10,000 ok, threw exceptions beyond that point.)
+
+How often does this happen? 
+100%
+
+Additional Information:
+Code compiled in MS.NET, and XSP run on Windows.  Mono Version 1.01.
+
+My last bug was a duplicate of a bug I couldn't find any way to search 
+for, even once I had read it.  Could not find it without entering the bug 
+number directly, as several of my search dropdowns didn't contain the 
+categories it was filed under.  Sorry if this is the same..