StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3891143
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-10-08T13:45:03.707
FavoriteCount
0
LastActivityDate
2010-10-08T14:36:05.907
LastEditDate
2010-10-08T14:36:05.907
LastEditorUserId
36305
OwnerUserId
36305
ParentId
3889432
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Here is a more generic solution. The names of the elements can be specified separately from the code: <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:my="my:my" exclude-result-prefixes="my"> <xsl:output omit-xml-declaration="yes" indent="yes"/> <xsl:strip-space elements="*"/> <my:newValues> <element1>Changed1</element1> <element2>Changed2</element2> <element3>Changed3</element3> </my:newValues> <xsl:variable name="vElements" select="document('')/*/my:newValues/*"/> <xsl:template match="*" name="identity" mode="copy"> <xsl:element name="{name()}"> <xsl:copy-of select="namespace::*[not(name()='my' or name()='xsl')]"/> <xsl:apply-templates select="node()|@*"/> </xsl:element> </xsl:template> <xsl:template match="*"> <xsl:if test="not($vElements[name()=name(current())])"> <xsl:call-template name="identity"/> </xsl:if> </xsl:template> <xsl:template match="group"> <xsl:copy> <xsl:apply-templates select="node()"/> <xsl:apply-templates select="$vElements" mode="copy"/> </xsl:copy> </xsl:template> </xsl:stylesheet> </code></pre> when this transformation is applied on the provided XML document: <pre><code><root> <group> <element1>SomeValue1</element1> <element2>SomeValue2</element2> </group> </root> </code></pre> the wanted, correct result is produced: <pre><code><root> <group> <element1>Changed1</element1> <element2>Changed2</element2> <element3>Changed3</element3> </group> </root> </code></pre> Note: The seemingly complicated processing that discards the <code>"xsl"</code> anf <code>"my"</code> namespaces is unnecessary when the to-be-modified elements are in their separate document. This code intentionally puts the to-be-modified elements in the same document as the xslt stylesheet for demonstration purposes. In practice, just an <code><xsl:copy-of select="$vModifiedDoc/*"></code> will be used.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXSLT: When element exists add it and change value otherwise add element with value
 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. 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. CO+1 Yes, this is the general solution I was thinking. It's a pain that few XSLT processor handle XML NAMES 1.1, because in that way you could reset the namespaces in the inline data in order to have a more compact code.
 singulars
 PostPostId
 PO
 UserUserId
 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.