Thanks very much. I'm thinking that I'm probably going to have to go to a model-less app because this is going to be much bigger given the breadth of what I'm trying to accomplish.
On Monday, July 16, 2012 4:52:56 PM UTC-4, Derek wrote: > > There should be no benefit to moving them to multiple model files. It > would have the same performance (or perhaps slower). > > The models file is processed on every page load, so it can get expensive > if you have a lot of tables defined in it. > I'm sure Bruno can chime in here, but here is his recipe for model-less > apps... > > http://www.web2pyslices.com/slice/show/1479/model-less-apps-using-data-models-and-modules-in-web2py > > > On Monday, July 16, 2012 1:45:23 PM UTC-7, wdtatenh wrote: >> >> I've got to move a bunch of stuff around to speed up my site particularly >> on the controller folder. My question is that I have nearly 50+ tables >> defined in my db.py file. Is there any benefit to splitting these tables >> into multiple model files? The tables belong to a single database and most >> use the auth_user table as a referenced table. >> >> I'm assuming that they're all going to get read in regardless, therefore, >> splitting things up into multiple model files wouldn't gain me anything or >> am I wrong? >> >> Thanks in advance. >> > --
