The problem is that once you dive in, all of the "cool" rails scoping (user.books.create...) fails and you start managing the relationships yourself (user.books << book.find_or_create). It feels "wrong", but as I'm diving in deeper it seems like the best solution is to create an intermediate class to handle the association management and keep the logic out of the controllers.
On Monday, December 31, 2012 9:26:09 PM UTC-8, Dave Aronson wrote: > > On Sun, Dec 30, 2012 at 7:59 PM, <[email protected] <javascript:>> > wrote: > > > As a user, I can add my favorite book to my book list. > > Another user adds the same book to their book list. > > > > There should only be one instance of the book in the database but 2 > > user/book associations. > > When someone wants to add their favorite, check the database to see if > it exists. What's the problem? > > -Dave > > -- > Dave Aronson, the T. Rex of Codosaurus LLC, > secret-cleared freelance software developer > taking contracts in or near NoVa or remote. > See information at http://www.Codosaur.us/. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/X6pe_0eHgdQJ. For more options, visit https://groups.google.com/groups/opt_out.
