On 17 January 2012 13:24, Mohamad El-Husseini wrote:
> @Jordan, thank you for the explanation. I'm having a hard time seeing what
> the relationships model looks like: id, user_id, blog_id,
> relationship_type_id? In that, the relationship_type_id decides if the
> relationship is a user or an edi
Bump
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/WT-AkUpfUnkJ.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To uns
@Jordan, thank you for the explanation. I'm having a hard time seeing what
the relationships model looks like: id, user_id, blog_id,
relationship_type_id? In that, the relationship_type_id decides if the
relationship is a user or an editor?
Blog
belongs_to organization
belongs_to editor throug
my rudimentary understanding... you need these all to be has_many :through
relationships and you need only one person model and new relationship
models to account for privileges.
user
has_many organizations, through memberships
organization
has_many users, through memberships
membership
belongs_
Mr. El-Husseini.
I'm also new to Rails Dev, so my opinion is kind of imature, but for this
instant, I really believe you should NOT be worring about those issues. If
I were you, I would first focus on worring about getting my app to work
properly, according to my specifications, strenghening my Obj
Newbie learning Rails and about to undertake my first real app. Please bare
with me, I'll try not to be long winded.
It's a blogging app where blogs belong to organizations, not users. An
organization can have many blogs, a blog can have many admins, and many
subscribers. There can be many orga
6 matches
Mail list logo
