Hello,
I am building a Webapp with Cake and love it very much. The
Application have about 30 models. The problem is, that it will
increase over the time. Now I wonder, if it could be better to divide
the Webapp into different CakeApps to reduce the amount of models per
CakeApp in future.
What
On Oct 25, 2007, at 10:34 AM, Freight wrote:
Hello,
I am building a Webapp with Cake and love it very much. The
Application have about 30 models. The problem is, that it will
increase over the time. Now I wonder, if it could be better to divide
the Webapp into different CakeApps to
On 10/25/07, Freight [EMAIL PROTECTED] wrote:
What do you think? How many models do you have succesfully in one
CakeApp? What do you think, is the max-number of possible Models, so
that Cake still works stable?
I don't think there is any limit to how many models you can use, but
it does
The problem is that if all your models are related, then even just
using one will mean that all model classes are loaded. We have an app
here with 34 models, and about 25 of them are associated (up to five
degrees of separation). These 25 models will be loaded for virtually
every page request,
