StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12591965
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-09-25T22:22:00.800
FavoriteCount
0
LastActivityDate
2012-09-26T05:50:19.333
LastEditDate
2012-09-26T05:50:19.333
LastEditorUserId
842
OwnerUserId
842
ParentId
12591767
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
One effective way I have seen is to use macros (an often hated tool). Macros have two features that can help make life much easier, the single hash '#' which can turn a parameter into a string, i.e. <code>#_name</code> will be translated into <code>"fieldName1"</code> and the double hash '##' which concatenate parameters with other things which in turn can expand new things, i.e. <code>STRUCT_##_type##_str</code> that will be translated into <code>STRUCT_int_str</code> which will be translated into <code>"%d"</code> First wrap the structure or "description" in macros i.e. into an own file (the-struct.def) <pre><code>STRUCT_BEGIN(s_my_struct) STRUCT_FIELD(int, fieldName1) STRUCT_FIELD(int, fieldName2) STRUCT_FIELD(int, fieldName3) STRUCT_END(s_my_struct) // Note that you can add more structs here and all will automatically get defined and get the print function implemented </code></pre> Then one can define the macros differently in places where one want to declare or implement things that should handle the struct. i.e. <pre><code>#define STRUCT_BEGIN(_name) struct _name { #define STRUCT_END(_name) }; #define STRUCT_FIELD(_type, _name) _type _name; #include "the-struct.def" // then undef them #undef STRUCT_BEGIN #undef STRUCT_END #undef STRUCT_FIELD </code></pre> and to make a function that prints the struct <pre><code>#define STRUCT_BEGIN(_name) void print_ ## _name(struct _name *s) { #define STRUCT_END(_name) } #define STRUCT_FIELD(_type, _name) printf("%s = " STRUCT_##_type##_str "\n", #_name, s->_name); #define STRUCT_int_str "%d" /* this is to output an int */ // add more types... #include "the-struct.def" // then undef them #undef STRUCT_BEGIN #undef STRUCT_END #undef STRUCT_FIELD #undef STRUCT_int_str </code></pre> other uses can be to auto-generate functions to ie swap bytes etc. Made a small example as a gist here <a href="https://gist.github.com/3786323" rel="nofollow">https://gist.github.com/3786323</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to generate C code automatically
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USepatel
UserOwnerUserId
1. USepatel
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
CommentsPostId
1. COBeaten to the punch...
 singulars
 PostPostId
 PO
 UserUserId
 USJeffrey Hantin

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.