Head First Design Patterns is an excellent book IMHO for OO application design. It's geared towards Java but it has excellent points. One of them being 'favor composition over inheritance'. The use of modules in Rails gives so much flexibility that I think going that route would be the best/simplest solution.
Pepe On Dec 10, 1:09 pm, Philip Hallstrom <[EMAIL PROTECTED]> wrote: > > On Dec 10, 3:02 am, Philip Hallstrom <[EMAIL PROTECTED]> wrote: > >> I don't know anything about your app, but if you don't use STI (ie. > >> you leave abstract_class = true) you'll never be able to tell the > >> difference b/n the two classes. > > >> That is... you could.. > > >> create a BlockSchedule with ID=1 > >> create a DaySchedule with ID=2 > > >> BlockSchedule.all => returns both records. > > > That's not true. With the parent class being an abstract class they'd > > be in two completely separate tables. > > Ah. Sweet! Didn't know that. Thought from your other message that > toggle just told rails to stop looking around for STI (and the type > field). Good to know! --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
