StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7122258
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-08-19T13:25:54.030
FavoriteCount
0
LastActivityDate
2011-08-20T14:18:27.567
LastEditDate
2011-08-20T14:18:27.567
LastEditorUserId
36305
OwnerUserId
36305
ParentId
7115917
PostTypeId
2
Score
8
ViewCount
0
LastEditorDisplayName
text
Body
Use: <pre><code>//page[@id=$yourId]/node()[not(self::page)] </code></pre> This selects all nodes that are not <code>page</code> and that are children of any <code>page</code> in the document, the string value of whose <code>id</code> attribute is equal to the string contained in <code>$yourId</code> (most probably you would substitute <code>$yourId</code> above with a specific, desired string, such as <code>'1'</code>). Here is a simple XSLT-based verification: <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output omit-xml-declaration="yes" indent="yes"/> <xsl:strip-space elements="*"/> <xsl:param name="pId" select="3"/> <xsl:template match="/"> <xsl:copy-of select="//page[@id=$pId]/node()[not(self::page)]"/> </xsl:template> </xsl:stylesheet> </code></pre> when this transformation is applied on the provided XML document (wrapped in a single top node to make it well-formed): <pre><code><pages> <page id='1'> <title>Page 1</title> <page id='2'> <title>Sub Page 1</title> </page> <page id='3'> <title>Sub Page 2</title> </page> </page> <page id='4'> <title>Page 2</title> </page> </pages> </code></pre> the wanted, correct result is produced: <pre><code><title>Sub Page 2</title> </code></pre> Do note: One assumption made is that an <code>id</code> value uniquely identifies a <code>page</code>. If this is not so, the proposed XPath expression will select all <code>page</code> elements whose <code>id</code> attribute has a string valu of <code>$yourId</code>. If this is the case and only one <code>page</code> element must be selected, the OP must specify which one of the many <code>page</code> elements with this <code>id</code> should be selected. For example, it may be the first: <pre><code>(//page[@id=$yourId]/node()[not(self::page)])[1] </code></pre> or the last: <pre><code>(//page[@id=$yourId]/node()[not(self::page)])[last()] </code></pre> or ...
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXpath: Select node but not specific child elements
 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. POXpath: Select node but not specific child elements
 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
 VTUpMod
CommentsPostId
1. COWhile this looks exactly right, it doesn't actually work.. I am not sure if there is something wrong with xpath in PHP's simple xml, but this returns multiple copies of the requested page???
 singulars
 PostPostId
 PO
 UserUserId
 USBen
2. CO@Ben: This may happen only if more than one `page` can have the same value of its `id` attribute. I have updated my answer to cover this case. I also provide a simple verification showing that the initial XPath expression selects exactly one `page` element if an `id` value uniquely identifies a `page`.
 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.