StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16531001
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-05-13T20:57:29.220
FavoriteCount
0
LastActivityDate
2015-11-20T13:06:26.777
LastEditDate
2015-11-20T13:06:26.777
LastEditorUserId
279871
OwnerUserId
279871
ParentId
16528329
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Your answer couldn't be much simpler, so no need to worry on that front. When writing code, but especially XSLT, the clarity of the code tends to be worth a lot more than its ultimate efficiency. As for the hardcoded element name and copying attributes, here's a start: <pre><code><xsl:template match="Report_Entry"> <xsl:variable name="parent-name" select="name()"/> <xsl:variable name="parent-attributes" select="@*"/> <xsl:for-each select="Event"> <xsl:element name="{$parent-name}"> <xsl:copy-of select="$parent-attributes"/> <xsl:copy-of select="../*[not(self::Event)]"/> <xsl:copy-of select="."/> </xsl:element> </xsl:for-each> </xsl:template> </code></pre> <code>variable</code>s are used to stash some of the context as it exists outside the <code>for-each</code>. <code>element</code> makes an element that's a look-alike for your original, no matter what it's called, and the first <code>copy-of</code> makes it more convincing by copying in the original's attributes as well. Now, if your data suddenly takes on attributes, you'll be ready. The non-hardcodedness of the name doesn't mean much in this case, but it would if, say, you were to factor out that part to a separate template and call it from multiple places: <pre><code><xsl:template name="collapse-the-thing"> <xsl:param name="context"/> <xsl:param name="sub-element-name" select="'Event'"/> <xsl:variable name="parent-name" select="name($context)"/> <xsl:variable name="parent-attributes" select="$context/@*"/> <xsl:for-each select="$context/*[name()=$sub-element-name]"> <xsl:element name="{$parent-name}"> <xsl:copy-of select="$parent-attributes"/> <xsl:copy-of select="../*[name()!=$sub-element-name]"/> <xsl:copy-of select="."/> </xsl:element> </xsl:for-each> </xsl:template> <xsl:template match="Report_Entry"> <xsl:call-template name="collapse-the-thing"> <xsl:with-param name="context" select="."/> </xsl:call-template> </xsl:template> <xsl:template match="Some_Other_Entry"> <xsl:call-template name="collapse-the-thing"> <xsl:with-param name="context" select="."/> <xsl:param name="sub-element-name" select="'Happening'"/> </xsl:call-template> </xsl:template> </code></pre> Hope that was enlightening. Enjoy!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFlatten nodes that have repeated child node using XSLT
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USpsmay
UserOwnerUserId
1. USpsmay
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COThanks a lot! That was really enlightening and helpful! :) I'll save your flexible example for later, and will make use of first one. BTW, if I want to apply other transformations while flattening the document, I can replace <xsl:copy-of select="%xpath%"> for <xsl:apply-templates select=%xpath%">, right?
 singulars
 PostPostId
 PO
 UserUserId
 USjackzee
2. COYeah, you could actually replace them (the latter two `copy-of`s) with any number of other things depending on what you're looking for the output to be. `apply-templates` will of course apply the top-level `template` rules to the matching children of the current node (which within the `for-each` is your `Event` element). See also the `mode` attribute if you'd like to apply a separate set of rules for just this case.
 singulars
 PostPostId
 PO
 UserUserId
 USpsmay

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.