Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are actually two different ways to compose XML Schema documents: <code>&lt;xs:import&gt;</code> and <code>&lt;xs:include&gt;</code>. xs:include is intended to be used when the namespace of the containing document is the same as the one being referenced, so it's not quite what you're looking for. xs:import is better for your situation when you need to reference all (or a subset) of elements in the referenced schema and they're in a different target namespace. There's a question here on the differences: <a href="https://stackoverflow.com/questions/2357943/whats-the-difference-between-xsdinclude-and-xsdimport">What&#39;s the difference between xsd:include and xsd:import?</a>. </p> <p>Anyway, back to this specific question. What you probably want is something like this:</p> <pre><code>&lt;?xml version="1.0" encoding="utf-8"?&gt; &lt;xs:schema xmlns="http://example.com/namespace/for/ElementB" targetNamespace="http://example.com/namespace/for/ElementB" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" xmlns:ea="http://example.com/namespace/for/ElementA"&gt; &lt;xs:import namespace="http://example.com/namespace/for/ElementA" schemaLocation="A.xsd" /&gt; &lt;xs:element name="ElementB"&gt; &lt;xs:complexType&gt; &lt;xs:sequence&gt; &lt;xs:element name="foo" type="xs:string" /&gt; &lt;xs:element name="bar" type="xs:string" /&gt; &lt;!-- This introduces a element named ElementA that uses the ComplexType ea:ElementA defined in A.xsd --&gt; &lt;xs:element name="ElementA" type="ea:ElementA" /&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; &lt;/xs:element&gt; &lt;/xs:schema&gt; </code></pre> <p>Though you'll need A.xsd to create a complex type for ElementA that you can use in B.xsd as shown.</p> <p>This arcticle has some good information/examples and includes a discussion of some of the different composability strategies: <a href="http://www.xfront.com/ZeroOneOrManyNamespaces.html" rel="noreferrer">http://www.xfront.com/ZeroOneOrManyNamespaces.html</a></p>
    singulars
    1. This table or related slice is empty.
    1. POXSD with elements from other namespace
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USdaveaglick
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POXSD with elements from other namespace
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThank you, that looks quite good, I’ll try that. One question though, where does the `ea:` namespace prefix come from? Or is that the `name` the type definition gets in `A.xsd`?
      singulars
      1. PO
      1. USpoke
    2. COJust scroll way to right on the code window - it's referenced as the last attribute in the xs:schema element: `xmlns:ea="http://example.com/namespace/for/ElementA"`. You could give it whatever prefix you want, just as you can for the default target namespace (though everyone always chooses `xs` or `xsd` by convention).
      singulars
      1. PO
      1. USdaveaglick
    3. COOh, didn’t bother to scroll that far and missed that, sorry xD Also thanks for your help, I’ll try this as soon as possible and post my results :)
      singulars
      1. PO
      1. USpoke
 

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