StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2516296
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-03-25T14:27:31.077
FavoriteCount
0
LastActivityDate
2010-03-25T17:36:00.930
LastEditDate
2010-03-25T17:36:00.930
LastEditorUserId
16549
OwnerUserId
16549
ParentId
2516266
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
Use Javascripts <a href="http://www.w3schools.com/jsref/jsref_encodeURIComponent.asp" rel="nofollow noreferrer">encodeURIComponent()</a>/decodeURIComponent() for "round-trip" encoding with .Net's URLEncode/URLDecode. EDIT As far as I know, historically the "+" has been used in URL encoding as a special substitution for the space char ( ASCII 20 ). If an implementation does not take the space into consideration as a special character with the '+' substitution, then it still has to escape it using its ASCII code ( hence '%20' ). There is a really good discussion of the situation at <a href="http://bytes.com/topic/php/answers/5624-urlencode-vs-rawurlencode" rel="nofollow noreferrer">http://bytes.com/topic/php/answers/5624-urlencode-vs-rawurlencode</a>. It's inconclusive, by the way. RFC 2396 lumps the space with other characters without an unreserved representation, which sides with the '%20' crowd. RFC 1630 sides with the '+' crowd ( via forum discusion )... <blockquote> Within the query string, the plus sign is reserved as shorthand notation for a space. Therefore, real plus signs must beencoded. This method was used to make query URIs easier to pass in systems which did not allow spaces. </blockquote> Also, the core RFCs are... <a href="http://tools.ietf.org/html/rfc1630" rel="nofollow noreferrer">RFC 1630</a> - Universal Resource Identifiers in WWW <a href="http://tools.ietf.org/html/rfc1738" rel="nofollow noreferrer">RFC 1738</a> - Uniform Resource Locators (URL) <a href="http://tools.ietf.org/html/rfc2396" rel="nofollow noreferrer">RFC 2396</a> - Uniform Resource Identifiers (URI): Generic Syntax
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POServer.UrlEncode(string s)... doesn't
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USkervin
UserOwnerUserId
1. USkervin
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POServer.UrlEncode(string s)... doesn't
 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.