Some time ago I overviewed model history and I realized that I don't
like a general idea - one model that logs everything. At that time
Django was studied how to create models dynamically (http://
code.djangoproject.com/wiki/DynamicModels) and I wrote small history
app for our purposes (of course,
On Tue, 2007-06-26 at 19:43 +, Thom Linton wrote:
> The 'fullhistory' branch has been lying dormant for a few months it
> seems (at least no commits to the django hosted branch) - so I've
> recently updated and implemented leftover functionality in a modified
> version of the branch.
>
> It i
On 6/26/07, Thom Linton <[EMAIL PROTECTED]> wrote:
> The method signature changed (slightly) to taste:
>- get_version(obj,rev) -> [Model]/None
>- get_version_by_date(obj,date) -> QuerySet/list()
>- get_history(obj,offset=0) -> QuerySet/list()
>
>- set_version(obj,rev) -> [Model]/No
Django-modelhistory is now living at [http://code.google.com/p/django-
modelhistory/]
Regards,
Thom
On Jun 26, 3:48 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> Hey Thom --
>
> This looks great at first glance -- many, many thanks!
>
> However, I'm not going to get much of a chance to
Hey Thom --
This looks great at first glance -- many, many thanks!
However, I'm not going to get much of a chance to review this for
inclusion for at least a few weeks, and possibly longer. I'd suggest
you set up a Google Code Hosting site for this and keep it up-to-date.
That way it can live as
The 'fullhistory' branch has been lying dormant for a few months it
seems (at least no commits to the django hosted branch) - so I've
recently updated and implemented leftover functionality in a modified
version of the branch.
It is undoubtedly imperfect, but it should work in common use cases
th
