StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PORails Basecamp style subdomains best practice
primarykey
Id
5024785
data
AcceptedAnswerId
0
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-02-17T03:30:33.703
FavoriteCount
10
LastActivityDate
2014-07-09T08:34:26.300
LastEditDate
2011-02-18T01:56:41.723
LastEditorUserId
64709
OwnerUserId
64709
ParentId
0
PostTypeId
1
Score
7
ViewCount
3480
LastEditorDisplayName
text
Body
My goal is to have separate user accounts for each subdomain. Under no circumstance do I want cross-pollination between subdomains. I've looked over <a href="http://www.robbyonrails.com/articles/2009/01/11/subdomain-accounts-with-ruby-on-rails-explained" rel="nofollow">Robby Russle</a>, and <a href="http://37signals.com/svn/posts/1512-how-to-do-basecamp-style-subdomains-in-rails" rel="nofollow">DHH's</a> thoughts (both are pre-Rails3 though). The controller handling is pretty straight forward, my questions is about keeping the model's data separated. What's the best way to keep user1 from seeing user2's data? Some idea's might include: <ol> <li>Add a <code>subdomain_id</code> foreign key to every model - Advantage, simple one-to-many relationship can be used to scope each model to a subdomain. - Disadvantage, this is pretty tight coupling between the data and the larger application logic, which seems inappropriate.</li> <li><code>One-to-many :through</code> for each model associating it with a subdomain - Advantage, no need to add a <code>subdomain_id</code> foreign key column to existing tables associating them with their sub domain. - Disadvantage, My gut feeling is that this is way overkill. Multiple join queries may get complicated and cross-pollination bugs may occur.</li> <li>Separate applications or databases for each subdomain - Advantage, the data is completely segregated. - Disadvantage, a large number of individual applications/databases will need to be managed/updated/secured/hosted/etc.</li> <li>Your idea?</li> </ol>
Tags
<ruby-on-rails><ruby-on-rails-3><multi-tenant>
Title
Rails Basecamp style subdomains best practice
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USSooDesuNe
UserOwnerUserId
1. USSooDesuNe
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PORails Basecamp style subdomains best practice
 UserUserId
 USJeff Paquette
 VoteTypeVoteTypeId
 VTFavorite
2. VO
 singulars
 PostPostId
 PORails Basecamp style subdomains best practice
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PORails Basecamp style subdomains best practice
 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.