Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>I. XSLT 1.0. This transformation uses simple <a href="http://www.jenitennison.com/xslt/grouping/muenchian.xml" rel="nofollow">Muenchian grouping</a></strong>:</p> <pre><code>&lt;xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"&gt; &lt;xsl:output omit-xml-declaration="yes" indent="yes"/&gt; &lt;xsl:key name="kChildByName" match="Query/*" use="name()"/&gt; &lt;xsl:template match= "Query/* [generate-id() = generate-id(key('kChildByName', name())[1]) ]"&gt; &lt;xsl:value-of select="name()"/&gt; &lt;xsl:text&gt;&amp;#xA;&lt;/xsl:text&gt; &lt;/xsl:template&gt; &lt;xsl:template match="text()"/&gt; &lt;/xsl:stylesheet&gt; </code></pre> <p><strong>When applied on the provided XML document</strong>:</p> <pre><code>&lt;ShopArea&gt; &lt;Connection name="Connection1"&gt; &lt;Report date="25-09-2011"&gt; &lt;Query id="1"&gt; &lt;TABLE1&gt;1.1&lt;/TABLE1&gt; &lt;TABLE2&gt;1.2&lt;/TABLE2&gt; &lt;TABLE3&gt;1.3&lt;/TABLE3&gt; &lt;/Query&gt; &lt;Query id="2"&gt; &lt;TABLE21&gt;2.1&lt;/TABLE21&gt; &lt;TABLE22&gt;2.2&lt;/TABLE22&gt; &lt;TABLE23&gt;2.3&lt;/TABLE23&gt; &lt;/Query&gt; &lt;/Report&gt; &lt;Report date="26-09-2011"&gt; &lt;Query id="1"&gt; &lt;TABLE1&gt;26 1.1&lt;/TABLE1&gt; &lt;TABLE2&gt;26 1.2&lt;/TABLE2&gt; &lt;TABLE3&gt;26 1.3&lt;/TABLE3&gt; &lt;/Query&gt; &lt;Query id="2"&gt; &lt;TABLE21&gt;26 2.1&lt;/TABLE21&gt; &lt;TABLE22&gt;26 2.2&lt;/TABLE22&gt; &lt;TABLE23&gt;26 2.3&lt;/TABLE23&gt; &lt;/Query&gt; &lt;/Report&gt; &lt;/Connection&gt; &lt;/ShopArea&gt; </code></pre> <p><strong>the wanted, correct result (all different names of elements that are children of a <code>Query</code>) is produced</strong>:</p> <pre><code>TABLE1 TABLE2 TABLE3 TABLE21 TABLE22 TABLE23 </code></pre> <p><strong>II. XSLT 2.0: This transformation uses</strong> <code>&lt;xsl:for-each-group&gt;</code>:</p> <pre><code>&lt;xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema"&gt; &lt;xsl:output omit-xml-declaration="yes" indent="yes"/&gt; &lt;xsl:template match="/*/*"&gt; &lt;xsl:for-each-group select="Report/Query/*" group-by="name()"&gt; &lt;xsl:sequence select="current-grouping-key(), '&amp;#xA;'"/&gt; &lt;/xsl:for-each-group&gt; &lt;/xsl:template&gt; &lt;xsl:template match="text()"/&gt; &lt;/xsl:stylesheet&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PONeed to fetch distinct elements through XSLT
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDimitre Novatchev
    1. USDimitre Novatchev
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PONeed to fetch distinct elements through XSLT
      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
    1. COExcellent! It works, but this code (Muenchian grouping) looks way too complicated. Will need a while to understand. Thank you very much.
      singulars
      1. PO
      1. USArvind Singh
    2. CO@Arvind Singh: You are welcome. Muenchian grouping is the de facto standard for highly efficient XSLT 1.0 grouping. To understand it better, just follow the link on the first line of this answer -- this leads to Jeni Tennison's excellent Muenchian Grouping page.
      singulars
      1. PO
      1. USDimitre Novatchev
 

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