maybe a wrong choice of wording but "disabling migrations and enabling fake migrations" REALLY turns out to be activated with migrate=True, fake_migrate=True.
migrate=False short-circuits at the highest level any migration logic, and it's the fastest "mode" to use on production, when you're - usually - sure that the model described in python and your backend are completely in-sync. tl;dr: migrate=False automatically discards any value you give to fake_migrate. Same applies for migrate and fake_migrate_all at the DAL() instantiation. On Friday, July 22, 2016 at 10:30:56 PM UTC+2, [email protected] wrote: > > I'm trying to add a field to my DB in GAE (which is a huge headache for > some reason?) and was taking a look at the book but noticed this > self-contradicting statement regarding migrations: > > The solution consists of disabling migrations for all tables and enabling > fake migrations: > > 1 > > db.define_table(...., migrate=True, fake_migrate=True) > > > Shouldn't it be "migrate=False, fake_migrate=True"? Or is the > introductory sentence wrong? > -- 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.
