On Tue, Jun 7, 2011 at 11:53 PM, Malcolm Box <malcolm....@gmail.com> wrote: > n 7 June 2011 15:16, Marc Aymerich <glicer...@gmail.com> wrote: >> >> Hi, >> I've activated the >> 'django.middleware.transaction.TransactionMiddleware' and I've >> decorated one method with @transaction.commit_on_success >> With this I expect that if the method raise an exception, django rolls >> back any database operation executed by this method, even the >> operations executed by submethods called by this main method, right? >> So I got this exception but the changes made on the DB during the >> method execution still there. >> > > What database are you using? Does it support transactions? >
Hi Malcolm and Christophe, You're right :) I'm using Mysql with myisam, I'm going to switch to InnoDB engine and try again. I thought that the transaction stuff were implemented in python and doesn't relay on DB backend. :( -- Marc -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
