Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Did you try this ?</p> <pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"&gt; &lt;xs:element name="ABC_HEADER" type="xs:string"/&gt; &lt;xs:element name="ABC"&gt; &lt;xs:complexType&gt; &lt;xs:sequence&gt; &lt;xs:element ref="ABC_HEADER"/&gt; &lt;xs:choice&gt; &lt;xs:element name="BODY_A"/&gt; &lt;xs:element name="BODY_B"/&gt; &lt;xs:element name="BODY_C"/&gt; &lt;/xs:choice&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; &lt;/xs:element&gt; &lt;/xs:schema&gt; </code></pre> <p>EDIT : Did you try inheritance schema with something like :</p> <pre><code>&lt;?xml version="1.0" encoding="utf-8" ?&gt; &lt;xs:schema elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema"&gt; &lt;xs:complexType name="ABC"&gt; &lt;xs:sequence&gt; &lt;xs:element ref="ABC_HEADER" /&gt; &lt;xs:element name="BODY" type="BODY" /&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; &lt;xs:complexType name="BODY"&gt; &lt;xs:sequence /&gt; &lt;/xs:complexType&gt; &lt;xs:complexType name="BODY_A"&gt; &lt;xs:complexContent mixed="false"&gt; &lt;xs:extension base="BODY"&gt; &lt;!-- define BODY_A schema here --&gt; &lt;/xs:extension&gt; &lt;/xs:complexContent&gt; &lt;/xs:complexType&gt; &lt;xs:complexType name="BODY_B"&gt; &lt;xs:complexContent mixed="false"&gt; &lt;xs:extension base="BODY"&gt; &lt;!-- define BODY_B schema here --&gt; &lt;/xs:extension&gt; &lt;/xs:complexContent&gt; &lt;/xs:complexType&gt; &lt;xs:complexType name="BODY_C"&gt; &lt;xs:complexContent mixed="false"&gt; &lt;xs:extension base="BODY"&gt; &lt;!-- define BODY_C schema here --&gt; &lt;/xs:extension&gt; &lt;/xs:complexContent&gt; &lt;/xs:complexType&gt; &lt;/xs:schema&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POCorrect schema for XML message with header and multiple body types
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPaciv
    1. USPaciv
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCorrect schema for XML message with header and multiple body types
      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. VTUpMod
    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. VTAcceptedByOriginator
    1. COThat seems to be the correct answer - will test to make sure first though. Thanks
      singulars
      1. PO
      1. USCarl Onager
    2. COI've marked this as the answer as it's the most correct one. However it does not produce the XML required so I've had to resort to handcoding the serialization in part
      singulars
      1. PO
      1. USCarl Onager
    3. COIn WCF, I would define a base class `BODY` and make every type of available body inherit from it. This should generate an other schema, see edit.
      singulars
      1. PO
      1. USPaciv
 

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