StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4360693
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2010-12-05T19:27:37.393
FavoriteCount
0
LastActivityDate
2010-12-05T19:27:37.393
LastEditDate
LastEditorUserId
0
OwnerUserId
36305
ParentId
4360310
PostTypeId
2
Score
12
ViewCount
0
LastEditorDisplayName
text
Body
Here is a generic "iterate" template that performs an action on an initial input and then on its result, until a given condition is specified. This transformation is tail-recursive and works without stack overflow with an intelligent XSLT processor: <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:my="my:my"> <xsl:output method="text"/> <my:action> <end>1000000</end> </my:action> <xsl:variable name="vAction" select="document('')/*/my:action"/> <xsl:template match="/"> <xsl:call-template name="iterate"> <xsl:with-param name="pAction" select="$vAction"/> <xsl:with-param name="pInput" select="0"/> </xsl:call-template> </xsl:template> <xsl:template name="iterate"> <xsl:param name="pAction"/> <xsl:param name="pInput"/> <xsl:if test="string-length($pInput)"> <xsl:variable name="vResult"> <xsl:apply-templates select="$pAction"> <xsl:with-param name="pInput" select="$pInput"/> </xsl:apply-templates> </xsl:variable> <xsl:copy-of select="$vResult"/> <xsl:call-template name="iterate"> <xsl:with-param name="pAction" select="$pAction"/> <xsl:with-param name="pInput" select="$vResult"/> </xsl:call-template> </xsl:if> </xsl:template> <xsl:template match="my:action"> <xsl:param name="pInput" select="0"/> <xsl:if test="not($pInput >= end)"> <xsl:value-of select="concat($pInput+1,'&#xA;')"/> </xsl:if> </xsl:template> </xsl:stylesheet> </code></pre> when this transformation is applied on any XML document (not used), an intelligent XSLT processor that optimizes tail recursion into iteration produces the wanted result without stack overflow. This is the case with Saxon 6.5.4, which I used to produce the result. Your problem is that not all XSLT processors recognize and optimize tail-recursion. For such processors, one can use DVC - style recursion: <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="text"/> <xsl:template match="/"> <xsl:call-template name="displayNumbers"> <xsl:with-param name="pStart" select="1"/> <xsl:with-param name="pEnd" select="1000000"/> </xsl:call-template> </xsl:template> <xsl:template name="displayNumbers"> <xsl:param name="pStart"/> <xsl:param name="pEnd"/> <xsl:if test="not($pStart > $pEnd)"> <xsl:choose> <xsl:when test="$pStart = $pEnd"> <xsl:value-of select="$pStart"/> <xsl:text>&#xA;</xsl:text> </xsl:when> <xsl:otherwise> <xsl:variable name="vMid" select= "floor(($pStart + $pEnd) div 2)"/> <xsl:call-template name="displayNumbers"> <xsl:with-param name="pStart" select="$pStart"/> <xsl:with-param name="pEnd" select="$vMid"/> </xsl:call-template> <xsl:call-template name="displayNumbers"> <xsl:with-param name="pStart" select="$vMid+1"/> <xsl:with-param name="pEnd" select="$pEnd"/> </xsl:call-template> </xsl:otherwise> </xsl:choose> </xsl:if> </xsl:template> </xsl:stylesheet> </code></pre> this transformation produces the correct result without any crash using MSXML4. With this DVC transformation the maximum recursion-depth is only Log2(N) -- in this case 19. I would recommend using the <a href="http://fxsl.sf.net" rel="noreferrer">FXSL library</a>. It provides DVC variants of commonly used higher-order functions, such as <code>foldl()</code> and <code>map()</code> making it possible to produce the DVC variant of almost any recursive algorithm. Of course, in XSLT2.0 one would simply write: <pre><code><xsl:sequence select="1 to 1000000"/> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPrint numbers from one to one million
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDimitre Novatchev
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPrint numbers from one to one million
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThanks, brilliant answer. I finally found a mistake in my approach. At the end it was quite a blunder. This floor(($start + $stop) div 2) was tricky for me.
 singulars
 PostPostId
 PO
 UserUserId
 USFlack
2. COAlthough I need some time to understand the first transformation :)
 singulars
 PostPostId
 PO
 UserUserId
 USFlack
3. CO+1 Complete answer.
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.

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.