Though search is of primary importance, object history is obviously very important as well -- both auditing (Audit Log pattern) and rolling back/comparing changes (Temporal Object pattern) are very common use cases (see Martin Fowler's treatment of these and some other patterns for things that change with time at http://martinfowler.com/ap2/timeNarrative.html ). It's nice that Marty has worked on it, but as Jacob said, it needs finishing. Audit Log, Temporal Object and Temporal Property patterns should be implemented and it should be possible to activate any combination of these. And there needs to be an intuitive way to access the snapshots. Considering its general applicability it should perhaps also be integrated in django.contrib.
P.S. s/abrastraction/abstraction/ in my previous post... what a bastardly word! On Mar 28, 10:32 pm, "Brian Armstrong" <[EMAIL PROTECTED]> wrote: > I think I will likely take your reply into consideration when > applying. Hopefully the mentors feel the same way, this looks like a > very fun project to work on. > > --Brian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---