Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Does this do what you want?</p> <pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"&gt; &lt;xsl:template match="/"&gt; &lt;output&gt; &lt;xsl:apply-templates select="//log | //result"&gt; &lt;xsl:sort select="@numerictimestamp"/&gt; &lt;/xsl:apply-templates&gt; &lt;/output&gt; &lt;/xsl:template&gt; &lt;xsl:template match="log | result"&gt; &lt;xsl:copy-of select="."/&gt; &lt;/xsl:template&gt; &lt;/xsl:stylesheet&gt; </code></pre> <p>I think that you were correct that the for-each was reducing the scope to just the current item</p> <p>The other thing that is happening is the converting your numerictimestamp attributes to numbers is causing rounding.</p> <p>If I do this:</p> <pre><code>&lt;xsl:template match="log | result"&gt; &lt;entry&gt; &lt;number&gt;&lt;xsl:value-of select="number(@numerictimestamp)"/&gt;&lt;/number&gt; &lt;string&gt;&lt;xsl:value-of select="@numerictimestamp"/&gt;&lt;/string&gt; &lt;/entry&gt; &lt;/xsl:template&gt; </code></pre> <p>I see this:</p> <pre><code>&lt;entry&gt; &lt;number&gt;20120123170428132&lt;/number&gt; &lt;string&gt;20120123170428133&lt;/string&gt; &lt;/entry&gt; &lt;entry&gt; &lt;number&gt;20120123170428352&lt;/number&gt; &lt;string&gt;20120123170428353&lt;/string&gt; &lt;/entry&gt; &lt;entry&gt; &lt;number&gt;20120123170428352&lt;/number&gt; &lt;string&gt;20120123170428352&lt;/string&gt; &lt;/entry&gt; </code></pre> <p>As I understand things, the XSLT number data type is according to IEEE 754 and wikipedia tells me that double precision is accurate to 15.95 digits. Your numbers are 17 digits</p>
    singulars
    1. This table or related slice is empty.
    1. POXSLT xsl:sort failing with large numbers and data-type="number"
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USKevan
    1. USKevan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POXSLT xsl:sort failing with large numbers and data-type="number"
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 - There's no need to apply templates inside a `for-each`. But I still don't understand why the OP's getting the output that he is. I'm probably being dumb.
      singulars
      1. PO
      1. USWayne Burkett
    2. CO@lwburk: Because `20120123170428353` and `20120123170428352` have exactly the same representation as doubles, which means that as doubles these two numbers are equal.
      singulars
      1. PO
      1. USDimitre Novatchev
    3. CO+1 for a good answer -- although the `<xsl:apply-templates>` inside `<xsl:for-each>` is correct, if somewhat weird.
      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