My code has a lot of tables that reference other tables, some with circular dependencies. Whenever I deploy to a new environment, I always get "table does not exist" when trying to resolve a "reference table_x" Field type, so I comment out every Field that contains a reference to another table and then revert changes once all the tables get defined. This works but is very tedious. It is infeasible for me to move around the table definitions due to the circular definitions and my preference for maintaining organizational structure.
Do people have an easier way to handle reference Field when deploying an application? If not, I am willing to contribute some code to accomplish this. Perhaps an option to the DB constructor where it creates the tables first but doesn't add any fields until later? -- 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.
