StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8620352
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-12-23T20:28:50.693
FavoriteCount
0
LastActivityDate
2011-12-23T20:28:50.693
LastEditDate
LastEditorUserId
0
OwnerUserId
36305
ParentId
8618681
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Here is the requested generic solution to the problem: <pre><code><xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:my="my:my" exclude-result-prefixes="my xs"> <xsl:import href="C:/temp/delete/GlobalTypeMappings.xsl"/> <xsl:output omit-xml-declaration="yes" indent="yes"/> <xsl:template match="order_system_a"> <order_system_b> <xsl:apply-templates select="@*"/> </order_system_b> </xsl:template> <xsl:template match="order_system_a/@type"> <xsl:attribute name="type" select= "my:convertType('order_system_a', 'order_system_b', .)"/> </xsl:template> </xsl:stylesheet> </code></pre> <h2>C:/temp/delete/GlobalTypeMappings.xsl:</h2> <pre><code><xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:my="my:my" exclude-result-prefixes="my xs"> <xsl:key name="kMapFromLocal" match="map" use="concat(@system, '+', @local-type)"/> <xsl:key name="kMapFromValue" match="map" use="concat(@system, '+', @value)"/> <my:TypeMappings> <map system="order_system_a" local-type="1" value="type1"/> <map system="order_system_a" local-type="2" value="type2"/> <map system="order_system_a" local-type="3" value="type3"/> <map system="order_system_a" local-type="4" value="type4"/> <map system="order_system_b" local-type="X" value="type1"/> <map system="order_system_b" local-type="Y" value="type2"/> <map system="order_system_b" local-type="Z" value="type3"/> <map system="order_system_b" local-type="T" value="type4"/>  </my:TypeMappings> <xsl:function name="my:convertType" as="xs:string?"> <xsl:param name="pfromSystem" as="xs:string"/> <xsl:param name="ptoSystem" as="xs:string"/> <xsl:param name="pfromValue" as="xs:string"/> <xsl:variable name="vthisDoc" select="document('')"/> <xsl:sequence select= "key('kMapFromValue', concat($ptoSystem, '+', key('kMapFromLocal', concat($pfromSystem, '+', $pfromValue), $vthisDoc ) /@value ), $vthisDoc ) /@local-type "/> </xsl:function> </xsl:stylesheet> </code></pre> When the above transformation is applied to the provided XML document: <pre><code><order_system_a type="1" /> </code></pre> the wanted, correct result is produced: <pre><code><order_system_b type="X"/> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODynamic variable access within XSLT
 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. PODynamic variable access within XSLT
 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
 VTAcceptedByOriginator
CommentsPostId
1. COThanks a lot, thats it!
 singulars
 PostPostId
 PO
 UserUserId
 USMork0075
2. CO@Mork0075: You are welcome.
 singulars
 PostPostId
 PO
 UserUserId
 USDimitre Novatchev

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.