It shouldn't be too hard to add a last-updated timestamp to a model, and compare it to a hidden field in the form validation.
-- dz On Wed, Mar 25, 2009 at 11:49 AM, Daniel Watkins <dan...@daniel-watkins.co.uk> wrote: > > Hello all, > > We recently ran into an issue when two people were editing a record via > the admin interface simultaneously. Both opened the record, made > changes and hit Save. Person A pressed Save after Person B, and so only > Person A's changes were reflected in the database. > > What is a good way of ensuring that this doesn't happen again? > > I would expect Person A to receive a warning about what they were about > to do, so they could open up Person B's changes in a different tab and > compare. An alternative solution would be to only allow one person to > be editing a page at a given time (where they are 'editing' between > opening the page and hitting 'Save', 'Save and add another' or logging > out). Perhaps a 'Cancel' button would also be in order. > > > Thanks, > > Dan > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
