StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15871626
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-04-08T05:02:46.337
FavoriteCount
0
LastActivityDate
2013-04-08T05:02:46.337
LastEditDate
LastEditorUserId
0
OwnerUserId
15168
ParentId
15871390
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Note that even before you permute the words, all of the following denote the same type: <ul> <li><code>long</code></li> <li><code>long int</code></li> <li><code>signed long int</code></li> <li><code>signed long</code></li> </ul> With permutations, you could have: <pre><code>long l0; long int l1; int long l2; signed long int l3; signed int long l4; long signed int l5; long int signed l6; int signed long l7; int long signed l8; signed long l9; long signed lA; </code></pre> Most sane people, most of the time, simply write <code>long</code> to denote this type. Your actual question is about when to use <code>long int</code> and when to use <code>int</code>. Technically, the range of values guaranteed by <code>int</code> is ±32,767 (or ±(215-1)). If you need values bigger than that, you should use <code>long</code>. However, you often find that <code>int</code> has a range of ±(231-1) (more or less). Sometimes, the range of <code>long</code> is the same as <code>int</code> (32-bit systems; 64-bit Windows); then the main reason for using <code>long</code> or <code>int</code> is to match the interface to a particular API (because the types are still distinct, even if they support the same range). Sometimes, the range of <code>long</code> is ±(263-1) (64-bit systems apart from 64-bit Windows); then you'd use <code>long</code> if you needed a range bigger than <code>int</code>. However, you might also consider using the 'portable' types from <code><inttypes.h></code> or <code><stdint.h></code> such as <code>int32_t</code> and <code>int64_t</code> instead. However, if the API uses a different type, you should probably use the API's type. If you intended to ask about when to use <code>long</code> and <code>long int</code>, then it is a matter of taste. I'd use plain <code>long</code> without any qualms. Unless there was a compelling reason for symmetry with some other declaration, I'd not use anything else.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUnder what circumstances can long int be used in C
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJonathan Leffler
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. This table or related slice is empty.
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.