StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
938295
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-06-02T07:18:51.497
FavoriteCount
0
LastActivityDate
2009-06-02T07:58:29.793
LastEditDate
2009-06-02T07:58:29.793
LastEditorUserId
42230
OwnerUserId
42230
ParentId
933942
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
By removing the Cumulative Maximum and adding 3 scripting functoids, doing the calculation in another way, the problem is solved. Mapping time decreased by a factor of 40. 11 Mb, 10 000 rows, was previously mapped in 200 minutes is now mapped in 5 minutes. Solution One scripting functoid, "Inline XSLT Call Template" with no input or output, containing the max() portion of the library from EXSLT <a href="http://www.exslt.org/math/functions/max/index.html" rel="nofollow noreferrer">Math library found here</a>. Instead of using the whole library I unzipped the file and "extracted" the max() template. <pre><code> <xsl:template name="GetMax"> <xsl:param name="nodes" /> <xsl:choose> <xsl:when test="not($nodes)">NaN</xsl:when> <xsl:otherwise> <xsl:for-each select="$nodes"> <xsl:sort data-type="number" order="descending" /> <xsl:if test="position() = 1"> <xsl:value-of select="number(.)" /> </xsl:if> </xsl:for-each> </xsl:otherwise> </xsl:choose> </xsl:template> </code></pre> One scripting functoid, "Inline XSLT Call Template" with no input or output, containing a variable which select attribute points at the template with the node set to calculate <pre><code><xsl:variable name="var:MaxValueDate"> <xsl:call-template name ="GetMax"> <xsl:with-param name ="nodes" select="Root//Parent/ValueToCalculate" /> </xsl:call-template> </xsl:variable> </code></pre> One scripting functoid, "Inline XSLT" with one output, using the variable to populate an output element with its value. <pre><code><OutputElement> <xsl:value-of select="$var:MaxValueDate" /> </OutputElement> </code></pre> Voila!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCumulative Maximum, calculate for every parent record
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USMartin Bring
UserOwnerUserId
1. USMartin Bring
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POCumulative Maximum, calculate for every parent record
 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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. 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.