On Sep 10, 2010, at 11:59 , Michael Pedersen wrote: > 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.
It would be a service that the database adapter would supply. Doesn't seem as though it would be difficult to do assuming the interface between the database adapter and the rest of the framework was structured the right way. Maybe it's something I'll look into writing. -- 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.
