What's missing is that many databases don't do transactions around these sorts of statements. Or, at the least, they didn't. create table, alter table, etc, all of these occur outside of transactions. Since more than PostgreSQL has to be accommodated, and PG is one of the few to support this. Even with its support for it, I honestly don't know if SQLAlchemy supports the idea of creating/dropping/altering tables in a transaction.
The idea is a good one. Unfortunately, from what I can tell, it's not something that can be done easily, if at all, in a cross-database fashion. On Fri, Sep 10, 2010 at 2:47 PM, Gisborne <[email protected]> wrote: > Guyren G Howe wrote: > > 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. > > Bump. No-one? > > -- > 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]<turbogears%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/turbogears?hl=en. > > -- Michael J. Pedersen My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected] -- 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.
