StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13889735
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-12-15T05:49:36.613
FavoriteCount
0
LastActivityDate
2012-12-15T05:49:36.613
LastEditDate
LastEditorUserId
0
OwnerUserId
1392723
ParentId
13889580
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
If <code>cFile</code> is a <code>char *</code>, indexing it like <code>cFile[posF]</code> is the same as doing <code>*(cFile + posF)</code>, or "give me the value of whatever is <code>posF</code> places from the start of the array." Your address-of operator (<code>&</code>) is unnecessary, and if it weren't, it would probably be the opposite of what you wanted (you want dereference — <code>*</code> — which is automatically done for you with the subscript notation). As other people have suggested, the correct code is most likely: <pre><code>lQueryData[posDB] = cFile[posF]; </code></pre> The reason you get the particular warning you do is because using <code>&cFile[posF]</code> gets the address of (i.e., a pointer to) the character in <code>cFile</code> at <code>posF</code>. However, when you then try to assign it to a place in the <code>lQueryData</code> array, it has to first cast that (internally) into a scalar type. A pointer is just a number that indexes into memory, and thus when used for anything but "pointing" to things, it's just an integer. Therefore, what you have is making an integer, from a pointer, without an explicit cast. You might consider compiling with <a href="http://clang.llvm.org" rel="nofollow">clang</a> instead of (what I presume is) GCC if you have access to it, it has much more accessible error messages. For instance, the error message for your code above is: warning: incompatible pointer to integer conversion assigning to 'char' with an expression of type 'char *'; remove & (with a little visual pointer to the offending "&" sign).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POC: a cast warning
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMatt Patenaude
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POC: a cast warning
 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
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.