On 4/24/07, robin_percy <[EMAIL PROTECTED]> wrote: > > What about doing both? Write a pre_save record indicating the > operation about to be attempted. And a post_save indicating the > success of the operation, using a unique identifier to identify the > pair. Then if the post_save gets out of sync, you have a record of > transactions that may be at fault.
I was considering something like that. But would it require two additional tables for every audited model? Or I could have just one table for writing post_save confirmation -- but how to create an identifier that is unique across several tables? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
