StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18361964
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-08-21T15:43:48.937
FavoriteCount
0
LastActivityDate
2013-08-21T15:43:48.937
LastEditDate
LastEditorUserId
0
OwnerUserId
1324394
ParentId
18361779
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
<code>POCollection</code> in sample.xml has default namespace <code>xmlns="http://www.amway.com/PurchaseOrder/1.0"</code> So why you define <code>xmlns:d="http://www.default.ns/</code> in your XSLT? <pre><code> <xsl:value-of select="/d:POCollection/ns1:PurchaseOrder/ns1:PurchaseOrderHeader/ns1:OUAddressLine1" />  <xsl:value-of select="/ns1:PurchaseOrder/ns1:PurchaseOrderHeader/ns1:OUAddressLine1" />  <xsl:value-of select="/POCollection/ns1:PurchaseOrder/ns1:PurchaseOrderHeader/ns1:OUAddressLine1" />  <xsl:value-of select="/POCollection/PurchaseOrder/PurchaseOrderHeader/OUAddressLine1" />  <xsl:value-of select="//OUAddressLine1" /> </code></pre> Edit: following should work <pre><code><?xml version="1.0"?> <xsl:stylesheet version="1.0" xmlns:amw="http://www.amway.com/PurchaseOrder/1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="text" /> <xsl:template match="/"> <xsl:value-of select="/amw:POCollection/amw:PurchaseOrder/amw:PurchaseOrderHeader/amw:OUAddressLine1" /> <xsl:text>|</xsl:text> <xsl:value-of select="//amw:PurchaseOrder/amw:PurchaseOrderHeader/amw:OUAddressLine1" /> <xsl:text>|</xsl:text> <xsl:value-of select="/amw:POCollection/amw:PurchaseOrder/amw:PurchaseOrderHeader/amw:OUAddressLine1" /> <xsl:text>|</xsl:text> <xsl:value-of select="//amw:OUAddressLine1" /> </xsl:template> </xsl:stylesheet> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXSLT on XML with Namespaces
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJirka Š.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POXSLT on XML with Namespaces
 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 for the edit! I was dismayed that you initially told me everything that was wrong, but not how to fix it.
 singulars
 PostPostId
 PO
 UserUserId
 USNate
2. COSorry for that... I was writing faster than thinking :) The main point IMO is that prefix of namespace is not important (may differs in xml and xslt) but URI it is assignig to is crucial. There were absolutely different URIs in your sample.xslt than in sample.xml - therefore nothing has been found.
 singulars
 PostPostId
 PO
 UserUserId
 USJirka Š.

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.