I was in the process of replying again to this last week but couldn't find a suitable link to point you to, sorry.
I was going to suggest searching for the subtype/supertype database design pattern.
Basically you have a supertype table which contains all attributes common to all subtypes and only put the different unique fields of the other types in the subtype tables (much like Scott has suggested above).
Sonic
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake PHP" 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
-~----------~----~----~----~------~----~------~--~---
- Re: Faking OO on RDBMS Sonic Baker
- Re: Faking OO on RDBMS [EMAIL PROTECTED]
