StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4599724
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-01-05T00:07:08.127
FavoriteCount
0
LastActivityDate
2011-01-31T19:42:37.213
LastEditDate
2011-01-31T19:42:37.213
LastEditorUserId
208809
OwnerUserId
208809
ParentId
4598409
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
Explanation for weird #text strings The weird #text strings dont come out of the blue but are actual Text Nodes. When you load a formatted XML document with <code>DOM</code> any whitespace, e.g. indenting, linebreaks and node values will be part of the DOM as <code>DOMText</code> instances by default, e.g. <pre><code><cellphones>\n\t<telefon>\n\t\t<model>Easy DB… E T E T E T </code></pre> where E is a <code>DOMElement</code> and T is a <code>DOMText</code>. To get around that, load the document like this: <pre><code>$dom = new DOMDocument; $dom->preserveWhiteSpace = FALSE; $dom->load('file.xml'); </code></pre> Then your document will be structured as follows <pre><code><cellphones><telefon><model>Easy DB… E E E T </code></pre> Note that individual nodes representing the value of a <code>DOMElement</code> will still be <code>DOMText</code> instances, but the nodes that control the formatting are gone. More on that later. Proof You can test this easily with this code: <pre><code>$dom = new DOMDocument; $dom->preserveWhiteSpace = TRUE; // change to FALSE to see the difference $dom->load('file.xml'); foreach ($dom->getElementsByTagName('telefon') as $telefon) { foreach($telefon->childNodes as $node) { printf( "Name: %s - Type: %s - Value: %s\n", $node->nodeName, $node->nodeType, urlencode($node->nodeValue) ); } } </code></pre> This code runs through all the telefon elements in your given XML and prints out node name, type and the urlencoded node value of it's child nodes. When you preserve the whitespace, you will get something like <pre><code>Name: #text - Type: 3 - Value: %0A++++ Name: model - Type: 1 - Value: Easy+DB Name: #text - Type: 3 - Value: %0A++++ Name: proizvodjac - Type: 1 - Value: Alcatel Name: #text - Type: 3 - Value: %0A++++ Name: cena - Type: 1 - Value: 25 Name: #text - Type: 3 - Value: %0A++ … </code></pre> The reason I urlencoded the value is to show that there is in fact <code>DOMText</code> nodes containing the indenting and the linebreaks in your <code>DOMDocument</code>. <code>%0A</code> is a linebreak, while each <code>+</code> is a space. When you compare this with your XML, you will see there is a line break after each <code><telefon></code> element followed by four spaces until the <code><model></code> element starts. Likewise, there is only a newline and two spaces between the closing <code><cena></code> and the opening <code><telefon></code>. The given type for these nodes is 3, which - <a href="http://de.php.net/manual/en/dom.constants.php" rel="nofollow">according to the list of predefined constants</a> - is <code>XML_TEXT_NODE</code>, e.g. a <code>DOMText</code> node. In lack of a proper element name, these nodes have a name of #text. Disregarding Whitespace Now, when you disable preservation of whitespace, the above will output: <pre><code>Name: model - Type: 1 - Value: Easy+DB Name: proizvodjac - Type: 1 - Value: Alcatel Name: cena - Type: 1 - Value: 25 Name: model - Type: 1 - Value: 3310 … </code></pre> As you can see, there is no more #text nodes, but only type 1 nodes, which means <code>XML_ELEMENT_NODE</code>, e.g. <code>DOMElement</code>. DOMElements contain DOMText nodes In the beginning I said, the values of <code>DOMElements</code> are <code>DOMText</code> instances too. But in the output above, they are nowhere to be seen. That's because we are accessing the <a href="http://de.php.net/manual/en/class.domnode.php#domnode.props.nodevalue" rel="nofollow"><code>nodeValue</code></a> property, which returns the value of the <code>DOMText</code> as string. We can prove that the value is a <code>DOMText</code> easily though: <pre><code>$dom = new DOMDocument; $dom->preserveWhiteSpace = FALSE; $dom->loadXML($xml); foreach ($dom->getElementsByTagName('telefon') as $telefon) { $node = $telefon->firstChild->firstChild; // 1st child of model printf( "Name: %s - Type: %s - Value: %s\n", $node->nodeName, $node->nodeType, urlencode($node->nodeValue) ); } </code></pre> will output <pre><code>Name: #text - Type: 3 - Value: Easy+DB Name: #text - Type: 3 - Value: 3310 Name: #text - Type: 3 - Value: GF768 Name: #text - Type: 3 - Value: Skeleton Name: #text - Type: 3 - Value: Earl </code></pre> And this proves a <code>DOMElement</code> contains it's value as a <code>DOMText</code> and <code>nodeValue</code> is just returning the content of the <code>DOMText</code> directly. More on nodeValue In fact, <code>nodeValue</code> is smart enough to concatenate the contents of any <code>DOMText</code> children: <pre><code>$dom = new DOMDocument; $dom->loadXML('<root>Hello World!!!</root>'); $node = $dom->documentElement->firstChild; // p printf( "Name: %s - Type: %s - Value: %s\n", $node->nodeName, $node->nodeType, $node->nodeValue ); </code></pre> will output <pre><code>Name: p - Type: 1 - Value: Hello World!!! </code></pre> although these are really the combined values of <pre><code>DOMText "Hello" DOMElement em with DOMText "World" DOMText "!!!" </code></pre> Printing content of a XML file using XML DOM To finally answer your question, look at the first test code. Everything you need is in there. And of course by now you have been given fine other answers too.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPrinting content of a XML file using XML DOM
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USGordon
UserOwnerUserId
1. USGordon
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPrinting content of a XML file using XML DOM
 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
 VTAcceptedByOriginator
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. COI liked other answers as they helped me quickly and easy, but this is so much more and I cannot express how much I appreciate this explanation. It is truly brilliant, Thank you SO much!
 singulars
 PostPostId
 PO
 UserUserId
 USSlavisa Perisic
2. CO@IWalkedAway you're welcome. Happy to help.
 singulars
 PostPostId
 PO
 UserUserId
 USGordon

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.