[Mono-bugs] [Bug 60470][Wis] Changed - Exception thrown when infering Xml Schema to DataSet
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Sun, 20 Jun 2004 14:49:36 -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=60470
--- shadow/60470 2004-06-19 16:36:37.000000000 -0400
+++ shadow/60470.tmp.27332 2004-06-20 14:49:35.000000000 -0400
@@ -2,13 +2,13 @@
Product: Mono: Class Libraries
Version: unspecified
OS: other
OS Details:
Status: NEW
Resolution:
-Severity:
+Severity: Unknown
Priority: Wishlist
Component: Sys.Data
AssignedTo: mono-bugs@ximian.com
ReportedBy: pbaena@uol.com.ar
QAContact: mono-bugs@ximian.com
TargetMilestone: ---
@@ -64,6 +64,20 @@
</xs:choice>
</xs:complexType>
</xs:element>
</xs:schema>
throws an exception in mono, and in .NET it is valid.
+
+------- Additional Comments From atsushi@ximian.com 2004-06-20 14:49 -------
+This is certainly different behavior. However, MS.NET did not design
+DataSet to accept XML Schema namespace (and thus schema document for
+InferXmlSchema()). DataSet schema feature does not work fine with
+MS.NET. Actually MS.NET infers only one table for xs:schema. This
+means, no child elements are validly infered.
+
+I am not sure but have one explaination about the reason why xs:schema
+is still infered as a table. InferXmlSchema() treats the document
+element as a DataTable when it has attributes (other than namespace
+nodes). The mystery is however why those attributes are not infered as
+columns. Anyways it sounds implementation-dependent problem and too
+cosmetic to dig in.