The main advantage is that I don't need to trigger table if something has changed in its definition, so databases/sql.log is updated after the first request. And statements from this file is put into database migration file that is run in production. So with lazy_tables=False I won't forget to track all database schema changes.
2014 m. kovas 7 d., penktadienis 12:16:54 UTC+2, Tim Richardson rašė: > > > With lazy_tables=True everything is ok, but in development environment I > don't want use True value. My table definitions are grouped in separate > files, so situation is next: >> >> > By the way, what development advantages do you find from not using > lazy_tables=True (which you will definitely use in production)? > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
