StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5547486
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-04-05T05:12:37.107
FavoriteCount
0
LastActivityDate
2011-04-05T05:12:37.107
LastEditDate
LastEditorUserId
0
OwnerUserId
87189
ParentId
5547153
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Based on your question, it sounds like you're trying to build an ACL and a metadata storage system at the same time. This can be a little tricky to sort out. Generally in a role-based system you have several patterns to follow, but usually some combination of the following: <ul> <li>Users have system-wide privileges based on a type of authentication level.</li> <li>Users have system-wide privileges that are granted by the user having one or more roles.</li> <li>Users have different privileges based on their authentication level in the context of specific resources.</li> </ul> You might be describing the first or second case depending on the nuances of it. Here's an example of the first: <pre><code>class User < ActiveRecord::Base belongs_to :role end class Role < ActiveRecord::Base # Defines methods to determine ACL privileges end </code></pre> The second is a bit more flexible, but is also slower when trying to resolve a simple yes/no case because more roles must be checked. <pre><code>class User < ActiveRecord::Base has_many :grants has_many :roles, :through => :grants end class Grant < ActiveRecord::Base belongs_to :user belongs_to :role # Defines methods to determine ACL privileges end class Role < ActiveRecord::Base # Defines methods used by Grant ACL implementation end </code></pre> If you need to have some kind of configuration or meta-data stored about what each role provides for the user, put that into the Grant model as additional fields.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POusers entity/table - Modeling this relationship
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UStadman
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POusers entity/table - Modeling this relationship
 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. 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.