StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11819341
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-08-05T19:19:31.797
FavoriteCount
0
LastActivityDate
2012-08-05T19:19:31.797
LastEditDate
LastEditorUserId
0
OwnerUserId
367456
ParentId
11796340
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
Just seeing that Salathe actually answered the same, but taking your comment into account and to stress this a bit more: You do not need to specify any DTD. As long as you use the <code>DOMDocument::loadHTML</code> or <code>DOMDocument::loadHTMLFile</code> functions, the HTML <code>id</code> attribute is actually registered for the the xpath <code>id()</code> function. With the demo HTML given in <a href="http://jsbin.com/elatum/2/edit" rel="noreferrer">http://jsbin.com/elatum/2/edit</a>, you even get an error when you load the document: <blockquote> Warning: DOMDocument::loadHTMLFile(): ID priceInfo already defined in ... </blockquote> Which is already a sign that this is a true ID attribute because it moans about duplicates. A related sample code looks like: <pre><code>$xpath = 'id("priceInfo")/div[@class="standardProdPricingGroup"]/span[1]'; $doc = new DOMDocument(); $doc->loadHTMLFile(__DIR__ . '/../data/file-11796340.html'); $xp = new DOMXPath($doc); $r = $xp->query($xpath); echo $xpath, "\n"; echo $r ? $r->length : 0, ' elements found', "\n"; if (!$r) return; foreach($r as $node) { echo " - ", $node->nodeValue, "\n"; } </code></pre> The output is: <pre><code>id("priceInfo")/div[@class="standardProdPricingGroup"]/span[1] 1 elements found - hello </code></pre> In case you need more control, first run an xpath to mark all HTML <code>id</code> attributes as ID for xpath: <pre><code>$r = $xp->query("//*[@id]"); if ($r) foreach($r as $node) { $node->setIdAttribute('id', true); } </code></pre> You can then use the same xpath with the <code>id()</code> function, no need to change it.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POTransform Javascript XPath in valid PHP query() XPath | normalize JS XPath --> PHP
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UShakre
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POTransform Javascript XPath in valid PHP query() XPath | normalize JS XPath --> PHP
 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. 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.