>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. MySQL might - if it is a MySQL with transactions. Oracle doesn't support it and I can't say anything on MSSQL. DDL-transactionality is definitely something you can't expect if you want to have support for multiple databases, so a backup/restore way of keeping the old state is much more portable. bye, Georg --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
