Wouldn't it be more useful to store the revision number as a field
instead of building a chain of links for the revision history? I'm not
sure how straightforward it is to fetch the record with the largest
revision number in Django though, but a boolean 'current' field would
be a quick work-around in that case.


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to