Object (not schema) versioning/history

[Vitaliy Fuks]

As I am thinking about using Django for a particular project I was
wondering if anyone ever considered keeping track of object content
history. For example, in a typical CMS/newspaper application with
multiple contributors I'd like to keep track of actual changes made to
some pieces of content by all users. Ultimately, I'd like to be able
to go through current "Changed field x, y, z." history entries, click
on them and see a diff-like output of actual changes made.

These records would be very infrequently accessed (in my worldview,
anyway), and perhaps generally infrequently created. I would love to
be able to put @versioned on top of a model and then have it
automatically create an app_model_history table and record things in it
appropriately on save().

Does that excite anyone else? SoC project? ;)

[Adrian Holovaty]

On 4/28/06, Vitaliy Fuks <vita...@gmail.com> wrote:
> These records would be very infrequently accessed (in my worldview,
> anyway), and perhaps generally infrequently created. I would love to
> be able to put @versioned on top of a model and then have it
> automatically create an app_model_history table and record things in it
> appropriately on save().
>
> Does that excite anyone else? SoC project? ;)

Hi Vitaliy,

Count me excited. Maybe you've already seen this, but Django's admin
provides an object history for each object edited in the admin, but
it's quite rudimentary -- it only saves changes made via the *admin*
(not via the Python API), and doesn't offer any diffs.

Adrian

--
Adrian Holovaty
holovaty.com | djangoproject.com