Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>@Dave is adding some dumb attribute to ChildB okay? Since your requirement on childB is 0-1 we can achieve the desired solution by adding a fixed attribute to childB and enforcing unique constraint on the attribute.</p> <pre><code>&lt;complexType name="childAType"&gt; &lt;simpleContent&gt; &lt;extension base="string"&gt;&lt;/extension&gt; &lt;/simpleContent&gt; &lt;/complexType&gt; &lt;complexType name="childBType"&gt; &lt;simpleContent&gt; &lt;extension base="string"&gt; &lt;attribute name="value" type="string" fixed="123"&gt;&lt;/attribute&gt; &lt;/extension&gt; &lt;/simpleContent&gt; &lt;/complexType&gt; &lt;element name="root"&gt; &lt;complexType&gt; &lt;choice minOccurs="0" maxOccurs="unbounded"&gt; &lt;element name="childA" type="tns:childAType" minOccurs="0" maxOccurs="unbounded"&gt;&lt;/element&gt; &lt;element name="childB" type="tns:childBType" minOccurs="0" maxOccurs="unbounded"&gt;&lt;/element&gt; &lt;/choice&gt; &lt;/complexType&gt; &lt;unique name="childB.max.once"&gt; &lt;selector xpath="./tns:childB"&gt;&lt;/selector&gt; &lt;field xpath="@value"&gt;&lt;/field&gt; &lt;/unique&gt; &lt;/element&gt; </code></pre> <p>Below is one of valid XML (order of B doesn't matter or B can be excluded)</p> <pre><code>&lt;tns:root xmlns:tns=" "&gt; &lt;tns:childA&gt;&lt;/tns:childA&gt; &lt;tns:childB&gt;&lt;/tns:childB&gt; &lt;tns:childA&gt;&lt;/tns:childA&gt; &lt;tns:childA&gt;&lt;/tns:childA&gt; &lt;/tns:root&gt; </code></pre> <p>However the below one is invalid</p> <pre><code>&lt;tns:root xmlns:tns=" "&gt; &lt;tns:childB&gt;&lt;/tns:childB&gt; &lt;tns:childA&gt;&lt;/tns:childA&gt; &lt;tns:childB&gt;&lt;/tns:childB&gt; &lt;tns:childA&gt;&lt;/tns:childA&gt; &lt;tns:childA&gt;&lt;/tns:childA&gt; &lt;/tns:root&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POHow to make a schema for an unordered list where some occur once, some many times
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBaski
    1. USBaski
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COSorry about the delay and thanks for trying but if I have understood this correctly ChildB nodes would have a valid "value" attribute, which I don't want, so it's not really ideal. I'll keep trying.
      singulars
      1. PO
      1. USDave
    2. CO@Dave XML instance need not have the attribute and it resides just in the xml schema. I couldnt think of other solutions either.
      singulars
      1. PO
      1. USBaski
    3. COHmm. The XML *need* not have the attribute, but if it did it would validate correctly, which is sort of messy. Or have I still misunderstood?
      singulars
      1. PO
      1. USDave
 

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