This is an example of a classic sub-type entity.
As was previously stated add all your common attributes to the parent
table. Performing an inner join on your foreign key between the
parent and sub-type entities will limit the result set to just the
specific sub-type you are interested in (i.e.
Hi, I think that can be achieved by adding this attribute to the parent
model instead.
Then all your models will inherit this property.
2008/9/18 Joe <[EMAIL PROTECTED]>
>
> Sounds like something that could be easily handled with EAV modeling.
> I wrote about it awhile ago. http://blog.joebeeson
Sounds like something that could be easily handled with EAV modeling.
I wrote about it awhile ago. http://blog.joebeeson.com/?p=30
There are plenty of other sources of good information on the topic.
With EAV you keep the number of tables small and it's still pretty
fast with smart indexing while
Hi bMilesp,
If I understood your requirement correctly, it sounds like a good
starting point would be for you to search on 'polymorphic'.
On Sep 18, 3:49 am, bMilesp <[EMAIL PROTECTED]> wrote:
> This is an interesting problem that i believe can have a reasonable
> solution using cakephp. i'm no
This is an interesting problem that i believe can have a reasonable
solution using cakephp. i'm not going to get into the background, but
it stems from this idea:
http://fornicode.com/2008/03/18/cakephp-a-has-either-association/
now for the business.
my current company has a custom built CMS an
