Maybe you could soft link the model files. For controller foo you would have a file models/foo/foo.py
If controller bar needs needs data from table foo, you would create a soft link in you models/bar directory to models/foo/foo.py. Note if you link it in as foo.py, it will run after bar.py, so you would want to name the link according to the necessary sequence. Don't know what this would do for migrations on the production box, though. On Friday, May 25, 2012 11:49:51 AM UTC-4, 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 >
