[Mono-bugs] [Bug 53959][Maj] Changed - DataSet does not write child rows correctly

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 15 Jun 2004 02:43:10 -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 atsushi@ximian.com.

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

--- shadow/53959	2004-06-15 01:24:40.000000000 -0400
+++ shadow/53959.tmp.24852	2004-06-15 02:43:10.000000000 -0400
@@ -2,21 +2,21 @@
 Product: Mono: Class Libraries
 Version: unspecified
 OS: Red Hat 9.0
 OS Details: 
 Status: REOPENED   
 Resolution: 
-Severity: 002 Two hours
-Priority: Blocker
+Severity: Unknown
+Priority: Major
 Component: Sys.Data
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: davidandrewtaylor@hotmail.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 URL: 
-Summary: Beta 3 DataSet problem round-tripping XML (Schema Inference Issue)
+Summary: DataSet does not write child rows correctly
 OtherBugsDependingOnThis: 51851[INCOMPLETE]
 
 Description of Problem:
 MONO 0.30: If I use ReadXml(input.txt) and then immediately call WriteXml
 (output.txt), the output format is incorrect.  Certain XML attributes 
 have been modified to be XML elements.  This appears to be a problem with 
@@ -170,6 +170,13 @@
 <FullTextResponse>
   <Domains />
 <FullTextResponse>
 
 Note the domain element is emply! (it should contain a few rows of 
 data).
+
+------- Additional Comments From atsushi@ximian.com  2004-06-15 02:43 -------
+You should not set severity without reading what it means, nor blocker
+priority without reading what it means.
+
+Attaching the patch.
+