StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10682710
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-05-21T09:31:14.643
FavoriteCount
0
LastActivityDate
2012-05-21T09:31:14.643
LastEditDate
LastEditorUserId
0
OwnerUserId
889949
ParentId
10682081
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
In order to see the content of an object in this manner, you would need to convert it to a string. If you wanted to do this, you could either simply <code>echo</code>/<code>print</code> it, or cast it to a string like this: <pre><code>$string = (string) $object; </code></pre> When an object is converted to a string, PHP calls it's <code>__toString()</code> method. Unfortunately a DOMElement object does not define one, so when you try and convert it to a string you will get the following error: <blockquote> Catchable fatal error: Object of class DOMElement could not be converted to string in... </blockquote> In this specific scenario, there is a poor man's work around that allows one to do this in a small amount code, and that is to bounce it through <a href="http://php.net/manual/en/book.simplexml.php" rel="nofollow">SimpleXML</a> using the <a href="http://php.net/manual/en/function.simplexml-import-dom.php" rel="nofollow"><code>simplexml_import_dom()</code></a> function - since the <code>SimpleXMLElement</code> class does define an <code>asXML()</code> method which will convert it back to an XML string. So you can do this: <pre><code>foreach($headerh1 as $match) { $xml = simplexml_import_dom($match); echo $xml->asXML(); } </code></pre> However, in this specific instance, this results in the following output: <pre><code><h1 id="h-top-questions">&#13; Top Questions &#13; </h1> </code></pre> So you see, there are some extra HTML entities leaking in there that were not in the original source code. This has happened somewhere between DOM and SimpleXML. In order to get around this, it would be possible to: <ul> <li>Pass the output through <a href="http://php.net/manual/en/function.html-entity-decode.php" rel="nofollow"><code>html_entity_decode()</code></a>. This is not a great option as it may result in invalid XML/HTML output.</li> <li>Roll your own function to convert a DOMElement to a string. This is also not a great option as it would be very complex, and you would potentially need to recurse through many levels to successfully retrieve a full node list.</li> </ul> However, one thing to keep in mind here is that what you are doing does not have much of a practical application for anything other than testing and debugging. One would never really want to output a partial document.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POEchoing Xpath w/ Dom
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDaveRandom
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. This table or related slice is empty.
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.