Reading this raised a view questions: Yes, by default, migrate=True. To turn off migrations for an entire DAL > connection, do: > > db = DAL(..., migrate_enabled=False) > > So it is possible to have one application that just contains the model and another application that contains the model with migrate_enabled=False and the controllers and views?
What happens to the auth_ tables in this case? Except for my custom auth_user table their definition is outside my model files. In case a migration in the application containing the model fails there are no consequences for the other application? In my table definitions I have migrate='table_name.table' and after migration I set migrate=False. Does migrate_enabled=False disable all instances of migrate='table_name.table' According to the book before doing db = DAL(...,fake_migrate_all=True) I make a copy of the databases folder, after that do I empty the databases folder? Kind regards, Annet -- --- 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.
