StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16125152
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-04-20T21:02:11.357
FavoriteCount
0
LastActivityDate
2013-04-20T21:02:11.357
LastEditDate
LastEditorUserId
0
OwnerUserId
3779
ParentId
763294
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
TL;DR Both terms are interchangeable (if what you mean is to convert some characters so they will be interpreted as plain string data). This debate is old. From <a href="http://cwe.mitre.org/data/definitions/116.html" rel="nofollow">CWE-116: Improper Encoding or Escaping of Output</a>: <blockquote> The usage of the "encoding" and "escaping" terms varies widely. For example, in some programming languages, the terms are used interchangeably, while other languages provide APIs that use both terms for different tasks. This overlapping usage extends to the Web, such as the "escape" JavaScript function whose purpose is stated to be encoding. Of course, the concepts of encoding and escaping predate the Web by decades. Given such a context, it is difficult for CWE to adopt a consistent vocabulary that will not be misinterpreted by some constituency. </blockquote> Comically enough JavaScript also has <code>encodeURIComponent()</code>, and its <a href="http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf" rel="nofollow">specification</a> avoids the debate entirely: <blockquote> The encodeURIComponent function computes a new version of a URI in which each instance of certain characters is replaced by one, two, three, or four escape sequences representing the UTF-8 encoding of the character. </blockquote> Personally I believe it's more appropriate to refer to the general process as "encoding", as you're creating a <a href="http://en.wikipedia.org/wiki/Code" rel="nofollow">code</a> to be transmitted through a communications channel (a piece of markup/programming code) and interpreted by a receiver (the parser). I think it's silly to replace <code><</code> with something completely different like <code>&#60;</code> and call that "escaping".
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXml Escaping/Encoding terminology
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USSteve Clay
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. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTDownMod
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.