StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5169059
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
11
CommunityOwnedDate
CreationDate
2011-03-02T14:41:03.067
FavoriteCount
0
LastActivityDate
2011-03-02T17:35:02.203
LastEditDate
2011-03-02T17:35:02.203
LastEditorUserId
36305
OwnerUserId
36305
ParentId
5168867
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
This transformation: <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="text"/> <xsl:strip-space elements="*"/> <xsl:template match="/"> Abstract: <xsl:text/> <xsl:for-each select="*/MT[starts-with(@N, 'Abstract')]"> <xsl:value-of select="@V"/> </xsl:for-each> Author: <xsl:text/> <xsl:for-each select="*/MT[starts-with(@N, 'Author')]"> <xsl:value-of select="@V"/> </xsl:for-each> </xsl:template> </xsl:stylesheet> </code></pre> when applied on the provided XML document: <pre><code><R N="14" MIME="application/pdf"> <RK>7</RK> <MT N="Abstract" V="Lorem Ipsum is simply dummy text of the printing " /> <MT N="Abstract1" V="and typesetting industry. Lorem Ipsum has been the industry's standard " /> <MT N="Author" V="Bernard Shaw;" /> <MT N="Author1" V="Mark Twain" /> <MT N="Abstract2" V="dummy text ever since the 1500s, when an unknown printer took a galley" /> <LANG>en</LANG> </R> </code></pre> produces the wanted result: <pre><code>Abstract: Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley Author: Bernard Shaw;Mark Twain </code></pre> Further refactoring: <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="text"/> <xsl:strip-space elements="*"/> <xsl:template match="/"> Abstract: <xsl:text/> <xsl:call-template name="concatAttributes"/> Author: <xsl:text/> <xsl:call-template name="concatAttributes"> <xsl:with-param name="pKeyStartString" select="'Author'"/> </xsl:call-template> </xsl:template> <xsl:template name="concatAttributes"> <xsl:param name="pKeyAttribName" select="'N'"/> <xsl:param name="pKeyStartString" select="'Abstract'"/> <xsl:param name="pValueAttribName" select="'V'"/> <xsl:for-each select= "*/MT[starts-with(@*[name()=$pKeyAttribName], $pKeyStartString)]"> <xsl:value-of select="@*[name()=$pValueAttribName]"/> </xsl:for-each> </xsl:template> </xsl:stylesheet> </code></pre> A second refactoring (requested by the OP): <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="text"/> <xsl:strip-space elements="*"/> <xsl:variable name="vAbstract"> <xsl:apply-templates mode="retrieve" select="//MT"/> </xsl:variable> <xsl:variable name="vAuthors"> <xsl:apply-templates mode="retrieve" select="//MT"> <xsl:with-param name="pKeyStartString" select="'Author'"/> </xsl:apply-templates> </xsl:variable> <xsl:template match="/"> Abstract: <xsl:value-of select="$vAbstract"/> Authors:: <xsl:value-of select="$vAuthors"/> </xsl:template> <xsl:template match="MT" mode="retrieve"> <xsl:param name="pKeyAttribName" select="'N'"/> <xsl:param name="pKeyStartString" select="'Abstract'"/> <xsl:param name="pValueAttribName" select="'V'"/> <xsl:if test="starts-with(@*[name()=$pKeyAttribName], $pKeyStartString)"> <xsl:value-of select="@*[name()=$pValueAttribName]"/> </xsl:if> </xsl:template> </xsl:stylesheet> </code></pre> EDIT: The OP has requested that "all processing should be done within the template matching <code>MT</code>". While this is possible in simple cases (see @Alejandro's answer), doing all the processing in a single template matching <code>MT</code> opens big gaps of unknowns. For example, it may be required to process other <code>MT</code> elements in a different way and in this case such processing will not be done at all. In more complex cases (such as when the elements and attributes come in any order, but the output must be sorted -- Abstract1, Abstract2, ..., Abstract-N), then the sort has to be specified explicitly and this has to be outside the template matching <code>MT</code>. Therefore, in the general case, it is not possible to produce the required output with code only within the template matching <code>MT</code>. I would recommend that the single template matching <code>MT</code> be in a named mode and that it should be used in "pull style" -- applied explicitly by the caller.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXSLT transformation, string concatenation
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDimitre Novatchev
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. POXSLT transformation, string concatenation
 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

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.