ok, so I took a look at the conditional models and I like it because it does seem to fit more correctly into the web2py setup.
Here is what I discovered (for those reviewing this later): - models/[controller]/[function] is the folder structure used to determine which model is executed - models/[insert_model_here].py -for- all requests - models/user/[insert_model_here].py -for- requests to controllers/user.py - models/user/view/[insert_model_here].py -for- requests to controllers/user.py -> def view(): Massimo: I wasn't able to find the patch from Mariano, do you have a link to that (or a discussion of that)? I did see some of his other posts and it looked like he was fighting the same battle I will be, so perhaps his changes would be beneficial. I certainly have a use case I can try them on for you. -David On Friday, May 25, 2012 6:46:41 PM UTC+1, Massimo Di Pierro wrote: > > Currently you can have models/ subfolders for controllers and for > functions in controllers. If two functions need the same model file, it > should go in the same models/controller/ subfolder or at the top level > (visible to all controllers). > > There is a proposal on the table (with a patch by Mariano) to allow > granular conditions models in which you can decide which model file is > needed by which controller or function. > > Is had been table because of lack of interest. I am happy to revive it if > there is push. > > massimo > > > > On Friday, 25 May 2012 10:49:51 UTC-5, David McKeone wrote: >> >> Hi Massimo, >> >> "You probably do not need 100 models defined for each request." and "Make >> sure you turn migrations off and bytecode compile your apps." >> >> No, I certainly don't need all 100 at all times. That was really just a >> test to see where the boundaries were going to be. It likely wasn't the >> optimal configuration (migrations were off, wasn't byte-compiled), but it >> did highlight that as the app grows that's an area I have to watch for and >> one that will affect the user experience. Once I saw that a boundary >> existed I found Bruno's model-less design and that brought things back to >> great performance levels. So I think that design will fit my needs >> performance wise. >> >> I'll investigate the conditional model system, but my understanding of >> that was that you would be restricted to specific controllers. As in, I >> can't use a single table (model) across multiple controllers. Would that be >> true? >> >> -David >> >
