Hello! Is there any way to tie file-system operations (or other non-database operations) to the transaction code? If the operation is found right in the view function it's simply a matter of moving the file operation to the end of the function and doing a rollback if it fails. However, if it happens inside several layers of function calls this becomes difficult.
Is there some sort of common Django or Python idiom for this sort of thing, an easy way to add hooks to the transaction middleware, or should I just stop being so paranoid about consistency? ;) Thanks! - Paul --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
