On Thu, Feb 26, 2009 at 4:03 AM, keymaster <[email protected]> wrote: > >> However, I do strongly advise _against_ using >> the behavior's Single Table inheritance option. In my opinion it is a >> very bad design/solution for subclassing purposes. > > If one was just coming out of University having taken a database > course or two, or an OO course or two, then yes, you would be correct > in saying Single Table Inheritance is for the uneducated. > > However, in the real world, where effort takes time and costs money, > and most applications are finite in size, there are some very > reasonable, and practical, tradeoffs that are employed. > > One of them is Single Table Inheritance. > > It is alot easier to manage, is very simple, and for reasonably small > object sets - it works just fine. You also save on performance by not > having to do extra table joins. > > So my recommendation is the opposite of yours in this case. For the > simple bookshelf app described above, I say yes, go with STI.
I'll second that. Both of you, actually. STI should never be considered as a first choice, IMO. But, neither should it not be considered at all. I'm using it now with a Cake app and it seems to be fine for my purposes. Although, I don't think I'd use it for the OP's project. I'd lean more towards CTI, though it is a bit more complex. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
