StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16129187
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-04-21T08:09:41.897
FavoriteCount
0
LastActivityDate
2013-04-21T11:15:37.523
LastEditDate
2013-04-21T11:15:37.523
LastEditorUserId
1141493
OwnerUserId
1141493
ParentId
16129186
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<code>Type const* p</code> is a pointer to const object with type <code>Type</code>. To be read left to right, with pointer pointing to type defined by everything before the star. The same way, <code>Type const* const q</code> is a const pointer to a const object with type <code>Type</code>. Also, <code>*p</code> cannot be modified through p. <code>p</code> is defined so as to const-point to <code>*p</code> and promise not to modify it. However, <code>*p</code>, p's pointee, can be modified by any other pointer pointing at it. For example, we can have <pre><code>Type t; Type const* pc = &t; Type *pnc = &t; </code></pre> <code>pc</code> promises not to alter t, <code>pnc</code> does not. Let's say class Type bears a const <code>inspect() const</code> method and a non-const <code>mutate()</code> method. Then we could have <pre><code>pc->inspect(); pnc->inspect(); pnc->mutate(); </code></pre> whereas this one would rise compiler's error: <pre><code>pc->mutate(); </code></pre> <code>Type const* const q</code> is a pointing to a const object and <code>*q</code> cannot be modified through q, just like with p. What is more, pointer <code>q</code> cannot be modified: it cannot be assigned a pointee a second time. Also, although this may sounds very strange, you are allowed to change in code the object of type <code>Type</code> pointed by pointer <code>Type const* p</code> -- but not through <code>p</code>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POC++ Type const* p and Type const* const p
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USoctoback
UserOwnerUserId
1. USoctoback
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POC++ Type const* p and Type const* const p
 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
 VTAcceptedByOriginator
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.