Also, Jon, keep in mind that Cake will attempt to create a model on the fly (basically AppModel) if it cannot find a model class for a particular table. So if you create a contact_emails table, for example, but you don't make a ContactEmail model class, then your app will still work - you just won't be able to make any custom code for your contact_emails table.
As Miles mentioned, however, less files isn't always best, and while you can run an app this way (i.e. letting Cake instantiate AppModel on the fly), you really should make all of your model files. - Jamie On Oct 18, 5:28 pm, Jon Lyles <[email protected]> wrote: > Dear robustsolution and Miles J, > > Thank you both for answering my question. > > On 10/18/09, Miles J <[email protected]> wrote: > > > > > > > Yes a model represents a database table and deals with the business > > logic for that table. So yes, you would most likely need 1 model per > > table. Less files is not always best. > > > On Oct 18, 8:16 am, robustsolution <[email protected]> wrote: > >> as for particular cases, I need more information > > >> On Oct 18, 6:13 pm, robustsolution <[email protected]> wrote: > > >> > Dear jonlyles > > >> > In general and if you stick to MVC then > > >> > M is required for each T (table) > > >> > C is for ZERO or more M > > >> > V is for 1 or more A (action) > > >> > A requires ZERO or 1 view > > >> > a for particular cases, I need more information > > -- > Sent from my mobile device --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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?hl=en -~----------~----~----~----~------~----~------~--~---
