there are actually two branches of the deal: - when dal migrations work out of the box - when they don't
Assuming the usual "work on dev, push to QA, test QA, if everything is ok push to PROD" workflow, you'd catch "when they don't" on QA. when they work out of the box, is pretty damn easy: push the code on QA, without transferring the databases/* folder, set migrate=True, hit appadmin, let the migration happen. if everything works fine, push to PROD is identical. -- 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.
