StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2860983
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-05-18T20:38:57.730
FavoriteCount
0
LastActivityDate
2010-05-18T20:38:57.730
LastEditDate
LastEditorUserId
0
OwnerUserId
18936
ParentId
2860777
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
<code>resolveExternals</code> and <code>substituteEntities</code> are parser features. They don't have an effect on serialisation. The XML infoset doesn't make any distinction whatsoever between: <pre><code><loc>http://www.somesite.com/serviços/redesign</loc> <loc>http://www.somesite.com/servi&#xE7;os/redesign</loc> <loc>http://www.somesite.com/servi&#231;os/redesign</loc> </code></pre> they all represent exactly the same information, any XML parser must treat them as identical, and XML serializers don't generally let you choose which to output. Normally you should just set the text node's value to include <code>ç</code> and let the serialiser write it to <code>ç</code>, as a raw UTF-8 byte string in the output. If you really must generate an XML file that contains only ASCII, so you can't use characters like <code>ç</code> directly, then tell PHP to use ASCII as the document encoding: <pre><code>$s= "serviços"; // or "\xC3\xA7" if you can't input UTF-8 strings directly $doc = new DOMDocument('1.0', 'US-ASCII'); $doc->appendChild($loc= $doc->createElement('loc')); $loc->appendChild($doc->createTextNode($s)); echo $doc->saveXML(); </code></pre> result: <pre><code><?xml version="1.0" encoding="US-ASCII"?> <loc>servi&#231;os</loc> </code></pre> However... having said all that, I still don't think this is right. Your value seems to be a URL, and non-ASCII characters aren't valid in URLs regardless of how they're encoded in the containing XML. It should be: <pre><code>http://www.somesite.com/servi%C3%A7os/redesign </code></pre> ie. <code>rawurlencode('serviços')</code>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPHP - DOM class - numbered entities and encodings problem
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USbobince
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPHP - DOM class - numbered entities and encodings problem
 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
CommentsPostId
1. COThanks for your inputs and clarifications. It wasn't exactly the solution I was looking for, but helped me a lot leading to the right path.
 singulars
 PostPostId
 PO
 UserUserId
 USDave

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.