On 7/15/06, Panard <[EMAIL PROTECTED]> wrote: >snip< > So, is it only the sqlite backend wich doesn't support recursive transactions, > or is django missing that point ? > If it's only a sqlite problem, is there a workaround?
In this situation, I'd be looking at writing my own decorator which counts how many transactons have been nested and only commits when control returns through the "outermost" level. You could store the nesting level in a thread local variable. You will need to be careful to define the semantics of exception recovery - for example, if method a raises an exception, which b catches and doesn't re-raise. a -- Alan Green [EMAIL PROTECTED] - http://bright-green.com --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
