Re: Ordered list of arbitrary objects

> 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.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to cake-php+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---