Am 28.02.2006 um 15:58 schrieb hugo: >> I'm not sure exactly what reparations you're thinking will be >> possible >> by rolling back a DDL transaction. I'm pretty sure most db's don't >> have full transaction control over DDL. Issuing a DDL statement >> usually involves at least an implicit commit, so, e.g., if something >> goes wrong three DDL commands into your evolution you're not going to >> be able to roll back to initial state. > > PostgreSQL and SQLite fully support transactioned DDLs.
Actually, PySQLite 2.x does an implicit commit after any DDL statement. I don't think this is enforced at the SQLite level, but supposedly the PySQLite author had reasons to do this in the bindings. Cheers, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
