I have been using Django for about a month now and I just moved over to the development version.
I am creating an application in which the client has dictated very stringent database record management in order to have a detailed audit trail on all changes made data. This does not necessarily mean logging. The rules are quite simple. · once saved, records are immutable. · records can not be deleted. they must be marked for deletion only. · to "edit" a record a new record is created with the new changes and a reference must point back to the old record · a comment must be attached to every edit or delete to explain why the action was taken. I was planning on doing this with a combination of Managers, Views and overriding the delete() and save() methods of my models. I have done some experimentation and found this to be awkward, not very elegant and to contravention of the DRY principle. Is there a better way of achieving this or am I on the right track? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
