Hi Paul, You might want to take a look at the third party packages listed under the *concurrency* category <https://www.djangopackages.com/grids/g/concurrentp-edit/>.
I've used django-concurrency <https://github.com/saxix/django-concurrency> in the past and it worked well for me. Simon Le mardi 25 novembre 2014 10:57:08 UTC-5, Paul Johnston a écrit : > > Hi, > > Consider an e-commerce site, where Alice and Bob are both editing the > product listings. Alice is improving descriptions, while Bob is updating > prices. They start editing the Acme Wonder Widget at the same time. Bob > finishes first and saves the product with the new price. Alice takes a bit > longer to update the description, and when she finishes, she saves the > product with her new description. Unfortunately, she also overwrites the > price with the old price, which was not intended. > > It's worth noting that the controller methods are thread-safe in > themselves. They use database transactions, which make them safe in the > sense that if Alice and Bob try to save at the precise same moment, it > won't cause corruption. The race condition arises from Alice or Bob having > stale data in their browser. > > Does Django have any way to prevent these race conditions? Just rejecting > the second edit with an "edit conflict" message would be a start - although > some intelligent merging would be even better. > > Thanks, > > Paul > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/0b766b15-d47a-4063-8768-01e70809f4d2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
