StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14066071
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-12-28T07:20:33.270
FavoriteCount
0
LastActivityDate
2012-12-28T07:20:33.270
LastEditDate
LastEditorUserId
0
OwnerUserId
1224374
ParentId
12242213
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Personally I would handle this as a single table inheritance model with a same-table association column. Put a field called <code>boss_id</code> on your users table. You'll have the main <code>User</code> model, that has the Sorcery authentication stuff and any common logic. Underneath it you have <code>Employer</code> and <code>Employee</code>. They have a method called <code>boss</code>: for the employer, this returns self or nil (whichever you find makes most sense), whereas for employees, this is an actual association method, something like this: <pre><code>class Employee < User belongs_to :boss, class_name: 'User' end </code></pre> When an employer sends out an invitation, direct the invitees to a URL for invitations specific to the employer, like: <a href="http://yoursite.com/employer/3/invitation" rel="nofollow">http://yoursite.com/employer/3/invitation</a> When the user creates their account you associate them to their owning employer. When an employer views their data, ensure that you pull their child employees' data as well, using the users table as a join table: <pre><code>class Employer < User has_many :employees, class_name: 'User', foreign_key: 'boss_id' has_many :contacts # Or whatever your application-specific stuff is # that you want employers to see through their employees has_many :employee_contacts, through: :employees, source: :contacts end </code></pre> If you need to assign ownership to employers in the database, I'd use an observer to watch for saves on the owned models, and if they are saved by someone with a <code>boss</code>, set an additional column to that boss' ID.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORuby on Rails 3.2 Sorcery authentication with sub users
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USVeraticus
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
 VTBountyClose
2. 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.