I would not store them in the same table. Store the common fields in one table and then use two other table to store the user type specific fields.
Why do you want to store all the information in one table? -----Original Message----- From: cake-php@googlegroups.com [mailto:cake-...@googlegroups.com] On Behalf Of kaushik Sent: Friday, December 26, 2008 8:40 AM To: CakePHP Subject: Problem in model designing I am going develop a system where there is two types of members. During registration or edit profile, there will be some common fields as well as some member type specific fields. Some of the common fields are mandatory, some are not. Same is true for member type specific fields. But both type of members will share same log in panel and other features. So I will like to store them in same table. But I am facing problem to create the model for it and write the validate code there. Anyone can give me any idea for that issue. --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
