It does make sense depending on the application. For example my project has USERS which then are divided up into 2 unique profile depending on the role of the user. Example EmployerProfile and EmployeeProfile. The Employer profile has different fields in the profile than say the Employee would. Sure I could combine the profiles into 1 db but I find it much easier when they are broken up into 2 tables. So when a USER registers they select their role and a profile is created for the role they have chosen.
Dave -----Original Message----- From: Braindead [mailto:markus.he...@gmail.com] Sent: January-28-09 7:07 PM To: CakePHP Subject: Re: Separating user and profile tables LunarDraco, thanks for the explanation! Now it's clear why Janne wants to separate the information. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
