Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The <code>key</code> element is not supposed to go inside the <code>sequence</code> element. Instead, you put it as a child of the <code>xs:element</code> that defines <code>ReferralCollection</code>. The <code>selector</code> and <code>field</code> are child elements of the <code>key</code> element that define what is supposed to be unique. Both are XPath expressions. The <code>selector</code> value sets up the XPath context, and the <code>field</code> elements (there can be more than one) define the combination of values that are supposed to be unique. So in your case, the <code>key</code> element might look something like this:</p> <pre><code>&lt;xs:key name="URL"&gt; &lt;xs:selector xpath="."/&gt; &lt;xs:field xpath="rd:keyword"/&gt; &lt;/xs:key&gt; </code></pre> <p>The <code>selector</code> here selects the element itself, that is, <code>ReferralCollection</code>. Then, in that context, the <code>field</code> element denotes the values of the <code>keyword</code> elements, which are thus constrained to be unique. The value of an element in XPath is its text content.</p> <p>I haven't done much with <code>key</code> elements (or XML Schema in general), so some details above might not be correct, but the basic idea is what I explained, so it should be easy to fix any mistakes I made. Oh, also note that I used the <code>rd</code> prefix for your <code>READOO</code> namespace; in my experience using explicit prefixes is always best when dealing with XPath, so you need the appropriate <code>xmlns:rd</code> attribute in your schema to make this work.</p> <p><strong>EDIT:</strong> So it seems you want something like this:</p> <pre><code>&lt;xs:element name="ReferralCollection"&gt; &lt;xs:complexType&gt; &lt;xs:sequence&gt; &lt;xs:element name="URL" maxOccurs="unbounded"&gt; &lt;xs:complexType&gt; &lt;xs:sequence&gt; &lt;xs:element name="stem" type="xsd:string"/&gt; &lt;xs:element name="keyword" maxOccurs="unbounded"&gt; ... &lt;/xs:element&gt; ... &lt;/xs:complexType&gt; &lt;xs:key name="URL"&gt; &lt;xs:selector xpath="./URL"/&gt; &lt;xs:field xpath="stem"/&gt; &lt;/xs:key&gt; &lt;/xs:element&gt; </code></pre> <p>Is this closer to what you meant? It has <code>URL</code> elements, one or more, each containing a <code>stem</code> element followed by one or more <code>keyword</code> elements. The <code>key</code> constraint should make the contents of the <code>stem</code> elements unique.</p>
    singulars
    1. This table or related slice is empty.
    1. POXML Schema - Key in sequence
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJaakkoK
    1. USJaakkoK
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POXML Schema - Key in sequence
      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
    1. COthanks for your help!, however, perhaps ironically, when I include the key within ReferralCollection, I am then given an error that complexType is invalid. If I put it within the complexType but outside of the sequence, I am again told that the key is invalid.
      singulars
      1. PO
      1. USNona Urbiz
    2. CODo you put the `key` element after the `complexType` element inside `ReferralCollection`? Because those two elements are acceptable only in that order.
      singulars
      1. PO
      1. USJaakkoK
    3. COI didn't until I looked @Rubens answer. So does this mean it's simply impossible to force the key to be in sequence? I'd really like to mandate that it come first. Also, would you mind explaining why you used the prefix (which I ended up having to delete actually for my validator) instead of the @ sign (whatsit mean?) that I see elsewhere? [my validator validates it with and without the @ sign interestingly]
      singulars
      1. PO
      1. USNona Urbiz
 

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