>From a high-level design perspective, implementing something like this in Cake would be about the same as in Ruby on Rails. As far as table/class design, you could have a Person class which extends Model, and is extended by SalesPerson, Designer etc. (allowing the use of shared logic).
To your point about having a type column, you could normalize your data either as you describe, or by creating a 'roles' table, where Person either belongsTo or hasOne Role (case depending on your design), where either 'people' has a 'role_id' field (Person belongsTo Role), or Role has a 'person_id' field (Person hasOne Role). Hope that helps. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
