StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
217679
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2008-10-20T06:53:20.780
FavoriteCount
0
LastActivityDate
2008-10-20T06:53:20.780
LastEditDate
LastEditorUserId
0
OwnerUserId
17249
ParentId
217591
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Here is just a small example of what you could do: file1.xml: <pre><code><foo> <bar>Text from file1</bar> </foo> </code></pre> file2.xml: <pre><code><foo> <bar>Text from file2</bar> </foo> </code></pre> index.xml: <pre><code><index> <filename>file1.xml</filename> <filename>file2.xml</filename> </code></pre> summarize.xsl: <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:exsl="http://exslt.org/common" extension-element-prefixes="exsl"> <xsl:variable name="big-doc-rtf"> <xsl:for-each select="/index/filename"> <xsl:copy-of select="document(.)"/> </xsl:for-each> </xsl:variable> <xsl:variable name="big-doc" select="exsl:node-set($big-doc-rtf)"/> <xsl:template match="/"> <xsl:element name="summary"> <xsl:apply-templates select="$big-doc/foo"/> </xsl:element> </xsl:template> <xsl:template match="foo"> <xsl:element name="text"> <xsl:value-of select="bar"/> </xsl:element> </xsl:template> </xsl:stylesheet> </code></pre> Applying the stylesheet to index.xml gives you: <pre><code><?xml version="1.0" encoding="UTF-8"?><summary><text>Text from file1</text><text>Text from file2</text></summary> </code></pre> The trick is to load the different documents with the document function (extension function supported by almost all XSLT 1.0 processors), to output the contents as part of a variable body and then to convert the variable to a node-set for further processing.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POConcatenating xml files
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USGerG
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POConcatenating xml files
 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
1. COThanks. I knew this was the approach, but couldn't remember how to do it. I'm now using the msxml node-set function instead of the exslt one you suggest (I know, I'm a heretic) and getting somewhere.
 singulars
 PostPostId
 PO
 UserUserId
 USRichard A

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.