StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15070660
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2013-02-25T15:40:19.960
FavoriteCount
0
LastActivityDate
2013-02-25T15:48:31.900
LastEditDate
2013-02-25T15:48:31.900
LastEditorUserId
2054185
OwnerUserId
2054185
ParentId
15070141
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
PROBLEM 1. For the first problem that you have you can use a key: <pre><code><xsl:key name="variable-key" match="//variable" use="@name" /> </code></pre> That key is going to index all variable elements in the document, using their name. So now, we can access any of those elements by using the following XPath expression: <pre><code>key('variable-key', 'X') </code></pre> Using this approach is efficient when you have a lot of variable elements. NOTE: this approach is not valid if each variable has its own scope (i.e. you have local variables which are not visible in different parts of the document). In that case this approach should be modified. PROBLEM 2. For mapping attributes you could use a template like the following: <pre><code> <xsl:template match="@baseType[. = 'int']"> <xsl:attribute name="baseType"> <xsl:value-of select="'Long'" /> </xsl:attribute> </xsl:template> </code></pre> The meaning of this transformation is: each time that we match a baseType attribute with int value, it has to be replaced by a Long value. This transformation would be in place for each @baseType attribute in the document. <hr> Using the described strategies a solution could be: <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" indent="yes" />  <xsl:key name="variable-key" match="//variable" use="@name" />  <xsl:template match="text()" />  <xsl:template match="@*"> <xsl:copy> <xsl:value-of select="." /> </xsl:copy> </xsl:template>  <xsl:template match="type[@baseType='structure']"> <Item> <xsl:apply-templates select="*|@*" /> </Item> </xsl:template>  <xsl:template match="variableInstance"> <Field>  <xsl:apply-templates select="@*|key('variable-key', @name)/@baseType" /> </Field> </xsl:template>  <xsl:template match="@baseType[. = 'structure']" />  <xsl:template match="@baseType[. = 'int']"> <xsl:attribute name="baseType"> <xsl:value-of select="'Long'" /> </xsl:attribute> </xsl:template> </xsl:stylesheet> </code></pre> That code is going to transform the following XML document: <pre><code> <code> <variable baseType="int" name="X" /> <type baseType="structure" name="Y"> <variableInstance name="X" /> </type> </code> </code></pre> into <pre><code><Item name="Y"> <Field baseType="Long" name="X"/> </Item> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXSLT: merge two tags using attribute from one, tag from another with a transform/mapping
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USPablo Pozo
UserOwnerUserId
1. USPablo Pozo
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. 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.