StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13993486
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
7
CommunityOwnedDate
CreationDate
2012-12-21T16:12:41.337
FavoriteCount
0
LastActivityDate
2014-09-29T13:58:27.123
LastEditDate
2014-09-29T13:58:27.123
LastEditorUserId
237091
OwnerUserId
237091
ParentId
4145823
PostTypeId
2
Score
25
ViewCount
0
LastEditorDisplayName
text
Body
UrlEncode is useful for query string values (so to the left or especially, right, of each =). <blockquote> In this url, foo, fooval, bar, and barval should EACH be UrlEncode'd separately: <a href="http://www.example.com/whatever?foo=fooval&bar=barval" rel="noreferrer">http://www.example.com/whatever?foo=fooval&bar=barval</a> </blockquote> UrlEncode encodes everything, such as ?, &, =, and /, accented or other non-ASCII characters, etc, into %-style encoding, except space which it encodes as a +. This is form-style encoding, and is best for something you intend to put in the querystring (or maybe between two slashes in a url) as a parameter without it getting all jiggy with the url's control characters (like &). Otherwise an unfortunately placed & or = in a user's form input or db value value could break things. EDIT: <a href="http://msdn.microsoft.com/en-us/library/system.uri.escapedatastring(v=vs.110).aspx" rel="noreferrer">Uri.EscapeDataString</a> is a very close match to UrlEncode, and may be preferable, though I don't know the exact differences. UrlPathEncode is useful for the rest of the query string, it affects everything to the left of the ?. <blockquote> In this url, the entire url (from http to barval) should be run through UrlPathEncode. <a href="http://www.example.com/whatever?foo=fooval&bar=barval" rel="noreferrer">http://www.example.com/whatever?foo=fooval&bar=barval</a> </blockquote> UrlPathEncode does NOT encode ?, &, =, or /. It DOES, however, like UrlEncode, encode accented/non-ASCII characters with % notation, and space also becomes %20. This is useful to make sure the url is valid, since spaces and accented characters are not. It won't touch your querystring (everything to the right of ?), so you have to encode that with UrlEncode, above.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHttpServerUtility.UrlPathEncode vs HttpServerUtility.UrlEncode
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USScott Stafford
UserOwnerUserId
1. USScott Stafford
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
 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. CO+1 This is the correct answer.
 singulars
 PostPostId
 PO
 UserUserId
 USZano

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.