StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18262476
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-15T21:49:17.857
FavoriteCount
0
LastActivityDate
2013-08-15T21:49:17.857
LastEditDate
LastEditorUserId
0
OwnerUserId
1477421
ParentId
18261305
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You've made a good start. And now you've bumped your shins on a classic slip that happens to everyone sooner or later: You've written an XPath expression like <code>Xboxspellen/Spellen/Spel[14]/Spelnaam</code> and expect it to match an element in your document. But the elements in your document are not named <code>Xboxspellen</code>, etc.: they are namespace-qualified, and all of them have a default namespace declaration (<code>xmlns="..."</code>) in scope, so their full (expanded) name is not <code>Xboxspellen</code> etc., but <code>{http://www.w3schools.com}Xboxspellen</code>, <code>{http://www.w3schools.com}Spellen</code>, etc. Correct the situation by making your XPath expressions and your XML agree on the names of things. In the usual case, this means: <ol> <li>Add a namespace declaration to your XSLT stylesheet, binding some prefix (it doesn't matter what prefix) to the namespace used in your XML: xmlns:w3s = "<a href="http://www.w3schools.com" rel="nofollow">http://www.w3schools.com</a>"</li> <li>Use that prefix in your XPath expressions: <pre><code><td><xsl:value-of select="w3s:Xboxspellen /w3s:Spellen /w3s:Spel[14] /w3s:Spelnaam" /></td> <td><xsl:value-of select="w3s:Xboxspellen /w3s:Spellen /w3s:Spel[14] /w3s:Prijs"/></td> </code></pre></li> </ol> (I've broken lines in the XPath for legibility; white space is legal in XPath expressions, and it's a good thing, too.) Now the XPath expression will match.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCan't retrieve info from xml document with xsl
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USC. M. Sperberg-McQueen
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
1. 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.