Hi, Second that - don't do one database per user. However you can have one model use different tables for each account. By way of example, I am nearly finished a (cake-based) app that allows users to put custom fields in their forms. Of the various approaches, I chose to set up a new table for each account in which to store the form input and to have new columns created in that table whenever a new input field was created (assuming the column doesn't already exist).
So, all input is stored in a model called Value and within that model I set the $useTable to false. When an account is created a new table is also created called #values where # is the id of the account. Finally in the app code I get the relevant account code and feed that to a function that uses setSource to dynamically set the source of the Value model to the correct table. Just ensure you call clearCache on your models after new account creation! The approach suggested by Grant above - giving each datatype an operator_id/user_id etc is a good way to go. You may ask, how do I get that into each datatype without writing lots of the same code in my app? An answer to that is the observer model (see the Bakery) which is just marvellous for that kind of thing. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
