StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5342191
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-03-17T16:34:45.647
FavoriteCount
0
LastActivityDate
2011-03-17T16:52:18.100
LastEditDate
2011-03-17T16:52:18.100
LastEditorUserId
18771
OwnerUserId
18771
ParentId
5341995
PostTypeId
2
Score
8
ViewCount
0
LastEditorDisplayName
text
Body
You did not <a href="http://php.net/manual/en/domxpath.registernamespace.php" rel="noreferrer">register the XML namespace</a> before the query. <pre><code>// register it $xpath->registerNamespace('kml', "http://earth.google.com/kml/2.1"); // and use it, too ! $query = $xpath->query("//kml:Placemark[kml:type='Public/Daily Fee']"); </code></pre> (the <code>ancestor::kml:Placemark</code> in your expression made no sense, I left it out.) The namespace prefix in the XPath query must be used even if the namespace in question is the default namespace of the XML document (like in your case). The element <code><kml xmlns="http://earth.google.com/kml/2.1"></code> is equivalent to <code><kml:kml xmlns:kml="http://earth.google.com/kml/2.1"</code>>. However, an XPath query of <code>/kml</code> is not equivalent to <code>/kml:kml</code>. The latter would match both elements (when the <code>kml</code> namespace is registered beforehand), the former would match none of them, no matter what you do. Also note that you do not need to use the same namespace prefix that is used in the XML document. Assume the XML document is this: <pre><code><kml:kml xmlns:kml="http://earth.google.com/kml/2.1"> <kml:Document /> </kml:kml> </code></pre> Then you could still do this: <pre><code>$xpath->registerNamespace('foo', "http://earth.google.com/kml/2.1"); $query = $xpath->query("/foo:kml/foo:Document"); </code></pre> and get back a correct result. Namespace prefixes are just a shorthand.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODOM XPath Query Help
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTomalak
UserOwnerUserId
1. USTomalak
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODOM XPath Query Help
 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
 VTAcceptedByOriginator
CommentsPostId
1. COAhhh thanks. But was the initial query right? I'm not getting any results, should i just be using $result->saveXML?
 singulars
 PostPostId
 PO
 UserUserId
 USJamie
2. CO@Jamie: I've changed the XPath in my answer, I forgot the `kml` prefix at one point myself. Should work now. Also note that you do not need the `ancestor::` part at all.
 singulars
 PostPostId
 PO
 UserUserId
 USTomalak

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.