Re: A "revision-controlled field" type?

2007-08-16 Thread Brian Morton
It sounds like what you need to build is a custom ForeignKey type of field that creates another table for that field. Then, you can store an arbitrary number of revisions of that field, along with versioning information, and a wrapper around diff that can perform the functions you mention. On

Re: A "revision-controlled field" type?

2007-08-16 Thread Derek Anderson
this does sound quite usefullet us know if you find one and/or roll your own. :) Tim Chase wrote: >> I'm not sure I really understand. It sort of sounds like you are >> talking about a CharField with a choices argument. Is what you're >> looking for more complex? > > No...a "choices"

Re: A "revision-controlled field" type?

2007-08-16 Thread Brian Morton
I'm not sure I really understand. It sort of sounds like you are talking about a CharField with a choices argument. Is what you're looking for more complex? Can you describe it in more detail? On Aug 16, 4:06 pm, Tim Chase <[EMAIL PROTECTED]> wrote: > Has there been any work on a

Re: A "revision-controlled field" type?

2007-08-16 Thread Jeremy Dunck
Not the same, but interesting: http://code.djangoproject.com/wiki/AuditTrail In general, I'd be tempted to make a file-based svn repo and map app/model/field into a URL, rather than try to make my own system. :) On 8/16/07, Tim Chase <[EMAIL PROTECTED]> wrote: > > Has there been any work on a

A "revision-controlled field" type?

2007-08-16 Thread Tim Chase
Has there been any work on a "RevisionControlledField" type? Likely, a standard text-field with some controls for selecting versions or branches thereof, and saving becomes a bit complicated. I'm looking for ideas/suggestions/caveats for such a field (and if such a beast already exists,