The benefit would probably be minimal, particularly if you are compiling the application. Greater benefit comes from only defining tables when you actually need them, but this can be achieved via other means (e.g., conditional models, lazy tables). That doesn't mean it's a bad idea to put some of your code in modules -- just probably not necessary until the app gets fairly large/complex.
Anthony On Wednesday, August 31, 2016 at 2:54:35 PM UTC-4, Scott Hunter wrote: > > Is there any benefit to putting the code to define the database tables in > a function that has been defined in a module, but gets called from a model, > performance-wise? > > - Scott Hunter > -- 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.
