yes, you are right, models executed on every request. but you can use, model less application (define table using modules, best practice if you have the same table that been used by more than 1 web2py app) or conditional models (response.models_to_run) In book you can see an advice :
- Minimize the code in models: do not define functions there, define functions in the controllers that need them or - even better - define functions in modules, import them and use those functions as needed. ref: http://web2py.com/books/default/chapter/29/04/the-core#Conditional-models http://web2py.com/books/default/chapter/29/06/the-database-abstraction-layer#Model-less-applications http://web2py.com/books/default/chapter/29/13/deployment-recipes#Efficiency-tricks best regards, stifan -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
