[Mono-bugs] [Bug 77262][Wis] Changed - [PATCH] Sqlite Support for
Multiple Result Sets
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Fri Jun 2 09:14:21 EDT 2006
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 tauberer at for.net.
http://bugzilla.ximian.com/show_bug.cgi?id=77262
--- shadow/77262 2006-05-30 22:57:56.000000000 -0400
+++ shadow/77262.tmp.29168 2006-06-02 09:14:21.000000000 -0400
@@ -2,13 +2,13 @@
Product: Mono: Class Libraries
Version: 1.1
OS: All
OS Details:
Status: NEW
Resolution:
-Severity:
+Severity: Unknown
Priority: Wishlist
Component: Sys.Data.SqlClient
AssignedTo: tsenganal at novell.com
ReportedBy: jhill at arcfocus.com
QAContact: mono-bugs at ximian.com
TargetMilestone: ---
@@ -113,6 +113,17 @@
------- Additional Comments From jhill at arcfocus.com 2006-05-30 22:57 -------
Created an attachment (id=17125)
Updated Sqlite patch to support returning multiple result sets
+
+------- Additional Comments From tauberer at for.net 2006-06-02 09:14 -------
+Ah, great. It looks good. I don't have experience with multiple
+result sets with any data adapter, but is there a difference between a
+data-returning statement that returned 0 rows and a non-data returning
+statement? That is, if a SELECT returns no rows, it won't create a
+result set, which may be confusing when trying to figure out which
+result set is which in the returned DataReader.
+
+Also, it would be good to replace the many occurrences of
+((SqliteResultSet)resultsets[current_resultset]) with a property access.
More information about the mono-bugs
mailing list