StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5861942
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-05-02T20:07:53.857
FavoriteCount
0
LastActivityDate
2011-05-02T20:22:17.323
LastEditDate
2017-05-23T10:24:27.860
LastEditorUserId
-1
OwnerUserId
8123
ParentId
5861604
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Look into how you're forward declaring MList in mlist.h. You use the syntax <pre><code> typedef struct mlist MList; </code></pre> This looks a little off to me. You're declaring a type of name MList. Note that with the above style of declaration, the compiler expects to see "struct mlist" or just the type name's MList when referring to this struct. (This <a href="https://stackoverflow.com/questions/1737710/c-structs-dont-define-types">question</a> may be helpful to you). However later on you definen a struct MList as follows: <pre><code>struct MList{ int size; struct Mlist_head hashtable[HASHSIZE]; }; </code></pre> Which makes the compiler expect afterwords to see things referred to with "struct MList". But in your fwd declaration, you just said that plain old "MList" without the struct is ok. The compiler may or may not be able to make sense of this confusion between the fwd declaration and your definition. Its made worse in that one is a tag name of the struct and the other is the struct's canonical name. This kind of thing makes my spidy sense tingle that something could be off and causing confusion between you and the compiler. I would just change how you forward declare to be consistent with how Mlist is used and see if that helps you. To do this change the above line to: <pre><code> struct MList; </code></pre> (then notice in mlist.h how you inconsistently use the struct keyword when referring to MList. Sometimes you do and sometimes you don't. this may also be causing problems w/ confusing your compiler. If you change to the above fwd declaration, use struct MList, not just MList) In other news, for: <pre><code>mlist.c:63:37: warning: assignment from incompatible pointer type </code></pre> You're assigning a MEntry to a MNode, which are of different types, so I would expect you to get the warning you're getting.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHashtable in C using linked lists
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USDoug T.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHashtable in C using linked lists
 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
 VTAcceptedByOriginator
CommentsPostId
1. COThanks, very good explination.
 singulars
 PostPostId
 PO
 UserUserId
 USbond425

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.