Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><em>rewritten entire answer after edit by OP</em></p> <p>My original understanding of the error was wrong. The error is thrown on the initialization of the serializer, <em>not</em> when you read your XML. You cannot use a colon <code>:</code> in a name. If you specify a namespace, do not specify the prefix. Actually, you hardly ever specify the prefix (which is just a placeholder for the namespace).</p> <p>After doing so, you already noticed that the value ends up <code>null</code>. The reason is that the serializer defaults to unqualified attributes. If you have qualified attributes, it assumes the attribute namespace is different than the element's namespace. This will work:</p> <pre><code>&lt;!-- this works (if namespaces are indeed different --&gt; &lt;ho:CODED-TYPE fx:BASE=DATA-TYPE="A_UINT16"...&gt; &lt;!-- this works, unqualified name takes namespace of parent element --&gt; &lt;ho:CODED-TYPE BASE=DATA-TYPE="A_UINT16"...&gt; &lt;!-- this fails, because XmlSerializer does not expect qualified attributes --&gt; &lt;ho:CODED-TYPE ho:BASE=DATA-TYPE="A_UINT16"...&gt; </code></pre> <p>This seems an odd bug. Here's <a href="http://support.microsoft.com/kb/816222" rel="nofollow noreferrer">somewhat similar report on this</a>n at MSDN, which helped me to the solution. Just mark the attribute as qualified. The following works with your input XML (note <code>XmlSchemaForm.Qualified</code>):</p> <pre><code>[XmlRoot(ElementName = "FIBEX", Namespace = "http://www.asam.net/xml/fbx")] public class FIBEX { [XmlElement("CODING", Namespace = "http://www.asam.net/xml/fbx")] public FIBEXCoding Coding { get; set; } } public class FIBEXCoding { [XmlElement("SHORT-NAME", Namespace = "http://www.asam.net/xml")] public string ShortName { get; set; } [XmlElement("DESC", Namespace = "http://www.asam.net/xml")] public string ShortDescription { get; set; } [XmlElement("CODED-TYPE", Namespace = "http://www.asam.net/xml")] public FIBEXCodedType Codedtype { get; set; } } public class FIBEXCodedType { [XmlAttribute("BASE-DATA-TYPE", Namespace = "http://www.asam.net/xml", Form=XmlSchemaForm.Qualified)] public string BaseDataType { get; set; } [XmlAttribute("CATEGORY")] public string Category { get; set; } [XmlAttribute("ENCODING")] public string Encoding { get; set; } [XmlElement("BIT-LENGTH", Namespace = "http://www.asam.net/xml")] public int BitLength { get; set; } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POXmlSerializer throws InvalidOperationException when having a namespace prefix in the attribute
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAbel
    1. USAbel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POXmlSerializer throws InvalidOperationException when having a namespace prefix in the attribute
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWooohaaa. There was an error in that post :-( wait a second please.
      singulars
      1. PO
      1. USyas4891
    2. CO@yas4891: please show the exact declaration of your input XML, including how the namespaces are declared. Also, show a minimized sample of input that fails you. Do you use a schema validator or is a DTD involved?
      singulars
      1. PO
      1. USAbel
    3. COYou really want me to post the complete XmlSource? That's roughly 7KB. How about we agree on the root element + the parent element of the element in question? My serialization works so far for the rest of the document, but not for this attribute in the "wrong" namespace. I managed to get another attribute ("xml:lang") working the way described above, but it doesn't work here.
      singulars
      1. PO
      1. USyas4891
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload