Hmm, And in terms of normal development, whereby having 100 tables would be considered large..? I think that if you really, really, really wanted to, you could probably put all of your model class defentions into one file; but there´s no escaping that there needs to be a model defenition for each table.
Possibly* the reason there is one class defenition per file is to a) keep things easy to manage/maintain and b) to anticipate coping with the point being debated over here: http://groups.google.com/group/cake-php/browse_thread/thread/29f857ffb25dd0e0/3c28aeff26fd9e82?hl=en#3c28aeff26fd9e82 Or it could just be considered a good design full stop ;) But I don´t know, and I´m only guessing. Cheers, AD7six --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
