1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59 | # -*- coding: UTF-8 -*-
from django.db import models
from datetime import datetime
class FullHistory(models.Model):
"""
Issues: Unique fields don't work (multiple versions of the same row may need to have the same value)
"""
date_created = models.DateTimeField(default=datetime.now, editable=False)
date_updated = models.DateTimeField(default=datetime.now, editable=False)
class Meta:
abstract = True
ordering = ('date_updated',)
def __init__(self, *args, **kwargs):
# History classes must end in 'History', others must not.
if self.__class__.__name__.endswith('History'):
self._history_class = True
else:
self._history_class = False
super(FullHistory, self).__init__(*args, **kwargs)
def save(self, *args, **kwargs):
if self._history_class:
self._save_history_instance()
else:
self._save_non_history_instance()
super(FullHistory, self).save(*args, **kwargs)
def _save_history_instance(self):
""" Save method for a History object.
"""
# This updated instance must become a new object,
# no updating is possible for history classes
self.id = None
def _save_non_history_instance(self):
""" Save method for a non-History object.
"""
# Duplicate and reassign parent.
for model, field in self._meta.parents.items():
if getattr(self, '%s_id' % field.name) is not None:
rel_obj = getattr(self, field.name)
rel_obj.id = None
rel_obj.save()
setattr(self, '%s_id' % field.name, rel_obj.id)
# Set the new update time on the non-archived version
self.date_updated = datetime.now()
def delete(self):
# Only delete if this is not a "history" version
if not self._history_class:
self.save()
super(FullHistory, self).delete()
|
Comments
Brilliant. Way to get around all the hard stuff in the AuditTrail wiki page in one fell swoop.
#
Thanks! I'll look at expanding on this and making it comprehensive. I've just realised what a cool snippet number I have. Excellent.
#
I am also highly interested in this, as we've done something similar at work. Originally we intended to do the history at the DB level, but after designing the models to support that (a custom model that did nothing but provide read access to history entries) we decided to use Django for it.
Looking forward to seeing what you come up with as you expand it!
#
Take a look at django-reversion. That has admin integration and will work on third party apps just by changing a line in their admin.py
#
is this currently working for you against django 1.1 rc?
when i try to use it, i get the following error on save of an "Employee" instance:
#