On Aug 11, 10:29 pm, Russell Keith-Magee <freakboy3...@gmail.com>
wrote:
> There are any number of ways to solve this problem by adding a field
> to the model (autofield with an 'edit number', timestamp tracking last
> edit time etc). However, these aren't really candidates for a general
> solution.
It didn't occur to me before, but would the History mechanism be any
use here? It must already be tracking edits.
> A few random thoughts:
Thanks very much for those. I am digesting them now :-) I like the
idea of doing this at the form level rather than adding anything to
the model.
> If this is a problem that interests you, then I encourage you to dig
> around. Developing the code to implement this fix will certainly give
> you a very good grounding in the internals of Django's form
> infrastructure. If you can find a clean way to implement this
> functionality, then we are certainly interested in integrating this
> into the Django core.
It definitely does, and if I can find a way to do it that would be
useful to others that would be wonderful. I'm extremely impressed with
Django in my limited-to-this-point use of it.
--~--~---------~--~----~------------~-------~--~----~
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
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
