Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Not sure why you would go bottom up instead of top down. I would match <code>/*/*</code> and create the result document there.</p> <p>Example...</p> <p><strong>XML Input</strong></p> <pre><code>&lt;root&gt; &lt;level_a&gt; &lt;level_b&gt; &lt;level_c&gt; &lt;level_d&gt; &lt;level_e/&gt; &lt;/level_d&gt; &lt;/level_c&gt; &lt;/level_b&gt; &lt;/level_a&gt; &lt;level_b&gt; &lt;level_c&gt; &lt;level_d&gt; &lt;level_d&gt; &lt;level_e/&gt; &lt;/level_d&gt; &lt;/level_d&gt; &lt;/level_c&gt; &lt;/level_b&gt; &lt;/root&gt; </code></pre> <p><strong>XSLT 2.0</strong></p> <pre><code>&lt;xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"&gt; &lt;xsl:output indent="yes" encoding="UTF-8"/&gt; &lt;xsl:strip-space elements="*"/&gt; &lt;xsl:template name="output"&gt; &lt;output level="{substring-after(name(),'level_')}"&gt; &lt;xsl:apply-templates/&gt; &lt;/output&gt; &lt;/xsl:template&gt; &lt;xsl:template match="/*/*" priority="1"&gt; &lt;xsl:result-document href="{generate-id()}.xml"&gt; &lt;output&gt; &lt;xsl:call-template name="output"/&gt; &lt;/output&gt; &lt;/xsl:result-document&gt; &lt;/xsl:template&gt; &lt;xsl:template match="*[starts-with(name(),'level_')]"&gt; &lt;xsl:call-template name="output"/&gt; &lt;/xsl:template&gt; &lt;/xsl:stylesheet&gt; </code></pre> <p><strong>File 1</strong> (name will be different because of <code>generate-id()</code>)</p> <pre><code>&lt;output&gt; &lt;output level="a"&gt; &lt;output level="b"&gt; &lt;output level="c"&gt; &lt;output level="d"&gt; &lt;output level="e"/&gt; &lt;/output&gt; &lt;/output&gt; &lt;/output&gt; &lt;/output&gt; &lt;/output&gt; </code></pre> <p><strong>File 2</strong> (name will be different because of <code>generate-id()</code>)</p> <pre><code>&lt;output&gt; &lt;output level="b"&gt; &lt;output level="c"&gt; &lt;output level="d"&gt; &lt;output level="d"&gt; &lt;output level="e"/&gt; &lt;/output&gt; &lt;/output&gt; &lt;/output&gt; &lt;/output&gt; &lt;/output&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POXSLT 2.0: Transforming an element including all ancestors without using a foreach
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDaniel Haley
    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
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for your answer but I may have oversimplified my example. Actually I need to start at "level_d" because my actual xml is much more complex. If you wish I can try to reproduce a more real life example. But basically I need to go use either ancestor::* or parent::* recursively...
      singulars
      1. PO
      1. USVlax
    2. CO@Vlax - Could you check to see if there is a descendant "level_d" (`match="/*/*[descendant::level_d]"`)? You could stop processing at "level_d" by adding a template to match it specifically. An updated example might help me understand why you would want to go backwards up the tree.
      singulars
      1. PO
      1. USDaniel Haley
    3. COSorry for my first version of the xml now it should reflect better the actual xml. If you look in the last version you will see that the first level_b element has many level_d elements down in his the tree. So my idea was to locate all level_d elements extract the ancestors and the get the children. Each level_d on a separate file. From the nested level_d I only need to care about the last in the tree, the others nested level_d upwards the tree doesn't need a separate file and are regarded only as ancestors.
      singulars
      1. PO
      1. USVlax
 

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