Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Well your problem starts here:</p> <pre><code>&lt;xs:element name="begin-line"&gt; &lt;xs:complexType&gt; &lt;xs:attribute name="class" type="xs:string" use="optional" /&gt; &lt;/xs:complexType&gt; &lt;/xs:element&gt; </code></pre> <p>What this means is that a "begin line" type has an attribute called class (Which means the tag can have an attribute class like so: <code>&lt;begin-line class="lineclass"&gt;</code>. However it is simply a type <code>xs:string</code> which means that all you get is a string.</p> <p>I also don't know if this is an option, but if your XML could be made to have closing tags like this line for instance: <code>&lt;begin-line class="indent"/&gt;and Damascus is its resting place.&lt;end-line class="br"/&gt;</code></p> <p>XML should be like this: <code>&lt;begin-line class="indent"/&gt;and Damascus is its resting place.&lt;/begin-line class="br"&gt;</code></p> <p>I believe that if all the "line" tags were closed properly then the XSD generator might have a better time trying to derive what is inside the "begin-line" XML tag. Indeed if this is possible then you could rename <code>begin-line</code> to <code>line</code> and <code>begin-chapter</code> to <code>chapter</code> which should make your XML much more readable.</p> <p>If it's not possible to update your code, then you are going to have to try your best with the string itself. I'm not sure if verses contain pure HTML, but if so you could parse the string inside the <code>begin-line</code> element as XML itself, using the library to jump between values and nodes (you might have to wrap a pair of tags around the string before trying to parse it though).</p> <p>Good luck :)</p>
    singulars
    1. This table or related slice is empty.
    1. POXSD and plain text
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USSpence
    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. COUnfortunately, this xml is what I have to deal with, no way around it. What do you think about doing some regex string replacing magic with the xml before a deserialize it? I was thinking turning all self-closing <begin-line /> tags to opening tags and then turning all <end-line class="br"/> tags to </begin-line> tags. What do you think?
      singulars
      1. PO
      1. USPaul Knopf
    2. CODepending on how large your sample of XML is that might take a while.
      singulars
      1. PO
      1. USSpence
 

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