I'm surprised to find that migrations in the latest TurboGears aren't run in a transaction. Since I'm using Postgres, they clearly should.
An obvious solution (a decorator that wraps the upgrade/downgrade functions with transaction commands) isn't working, and besides, you'd really want the whole sequence of migrations wrapped in an outer transaction, I'm wondering if I'm just missing a setting or something. -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
