Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Does this meet your needs?</p> <pre><code> &lt;xs:element name="MyType" type="MyType.Type"/&gt; &lt;xs:complexType name="MyType.Type"&gt; &lt;xs:sequence&gt; &lt;xs:group ref="CollectedTypeGroup" minOccurs="0" maxOccurs="unbounded"/&gt; &lt;xs:choice minOccurs="0"&gt; &lt;xs:sequence&gt; &lt;xs:element name="MyType.PropertyOne" type="PType1.Type"/&gt; &lt;xs:group ref="CollectedTypeGroup" minOccurs="0" maxOccurs="unbounded"/&gt; &lt;xs:sequence minOccurs="0"&gt; &lt;xs:element name="MyType.PropertyTwo" type="PType2.Type"/&gt; &lt;xs:group ref="CollectedTypeGroup" minOccurs="0" maxOccurs="unbounded"/&gt; &lt;/xs:sequence&gt; &lt;/xs:sequence&gt; &lt;xs:sequence&gt; &lt;xs:element name="MyType.PropertyTwo" type="PType2.Type"/&gt; &lt;xs:group ref="CollectedTypeGroup" minOccurs="0" maxOccurs="unbounded"/&gt; &lt;xs:sequence minOccurs="0"&gt; &lt;xs:element name="MyType.PropertyOne" type="PType1.Type"/&gt; &lt;xs:group ref="CollectedTypeGroup" minOccurs="0" maxOccurs="unbounded"/&gt; &lt;/xs:sequence&gt; &lt;/xs:sequence&gt; &lt;/xs:choice&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; &lt;xs:group name="CollectedTypeGroup"&gt; &lt;xs:choice&gt; &lt;xs:element name="CollectedType" type="CollectedType.Type"/&gt; &lt;xs:element name="DerivedCollectedType" type="CollectedType.Type"/&gt; &lt;xs:element name="DerivedCollectedType2" type="CollectedType.Type"/&gt; &lt;/xs:choice&gt; &lt;/xs:group&gt; &lt;xs:complexType name="CollectedType.Type"&gt; &lt;xs:attribute name="name" type="xs:string"/&gt; &lt;/xs:complexType&gt; &lt;xs:complexType name="PType1.Type"&gt; &lt;xs:sequence&gt; &lt;xs:element name="PType1"&gt; &lt;xs:complexType&gt; &lt;xs:attribute name="Value" type="xs:string"/&gt; &lt;/xs:complexType&gt; &lt;/xs:element&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; &lt;xs:complexType name="PType2.Type"&gt; &lt;xs:sequence&gt; &lt;xs:element name="PType2"&gt; &lt;xs:complexType&gt; &lt;xs:attribute name="Value" type="xs:string"/&gt; &lt;/xs:complexType&gt; &lt;/xs:element&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POHow can I mix unbounded groups with restricted groups in a complexType?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAlohci
    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. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWow, that was a bunch of work... however it violates #1--Elements added must not be restricted to a particular order. Members of CollectedTypeGroup must be added before the property elements. This restriction has no valid meaning for what I'm trying to do...
      singulars
      1. PO
      1. USWill
    2. COI'm not clear what restriction is violated here. Could you post an actual example that doesn't validate?
      singulars
      1. PO
      1. USAlohci
    3. COI can add MyType.PropertyOne more than once.
      singulars
      1. PO
      1. USWill
 

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