On Fri, Jan 17, 2014 at 5:18 AM, Arnon Marcus <[email protected]> wrote: > A database scema is a description of the structure of a database - it has > nothing to do with requests. > You are talking about a convinience-feature that could have been implemented > differently - this coupling is convinient but makes no sense from a > performance standpoint. > I am looking for a way around that...
migrate=False is here to accomplish that. BTW, I think we have a misunderstanding point here. migrate=True is usefull mainly in development environment and it's an excellent feature, avoiding you to run command from shell, in a Django style. Change your model and know the db schema will be in sync with it autmatically is a great feature. It allows you to practice baby steps in your db structure. In development environment. On the other hand, migrate=True on production servers is a really bad practice. In production machines, your database user shouldn't have access to run DDL statements. It's a security commandment, right? So, in a system running in production, migrate=True should raise a grant error when it tries to sync db schema. migrate=True is our good friend, but just for dev environment. -- Vinicius Assef -- 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/groups/opt_out.
