On Tue, Aug 11, 2009 at 11:06 PM, Russell Keith-Magee<freakboy3...@gmail.com> wrote: > > On Wed, Aug 12, 2009 at 10:55 AM, David<da...@davidfindlay.org> wrote: >> >> >> >> 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. > > An interesting thought. I can't think of any obvious technical reason > that the admin Log combined with a timestamp on form submission > couldn't be used. You would need to dig into specifics to see if there > are any complications, but this is certainly worth looking into. > > This would fit into the same camp as the checksum solution - it would > tell you that a concurrent edit has occurred, but wouldn't tell you > how to resolve the concurrent edit. > > Another cause for hesitation is that it would be an admin-specific > solution to the problem. A generic solution that would work for all > ModelForms would be nice if it is possible. However, a working > solution in admin would be better than a theoretical but non-existent > solution in forms. > > Yours, > Russ Magee %-) > > > >
The problem with anything relying on AdminLog is it doesn't work if something is changed outside the admin. Personally I think including a JSON dump of the model with the page is the easiest solution, but I could be convinced otherwise. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Voltaire "The people's good is the highest law." -- Cicero "Code can always be simpler than you think, but never as simple as you want" -- Me --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
