django-concurrency 1.0

Optimistic lock implementation for Django. Prevents users from doing concurrent editing.

django-concurrency is an optimistic lock [1] implementation for Django.

Supported Django versions: 1.7.x 1.8.x, 1.9rc1.

It prevents users from doing concurrent editing in Django both from UI and from a django command.

How it works

sample code:

from django.db import models
from concurrency.fields import IntegerVersionField

class ConcurrentModel( models.Model ):
    version = IntegerVersionField( )
    name = models.CharField(max_length=100)

Now if you try:

a = ConcurrentModel.objects.get(pk=1)
a.name = '1'

b = ConcurrentModel.objects.get(pk=1)
b.name = '2'

a.save()
b.save()

you will get a RecordModifiedError on b.save()

Similar projects

Other projects that handle concurrent editing are django-optimistic-lock and django-locking anyway concurrency is “a batteries included” optimistic lock management system, here some features not available elsewhere:

• can be applied to any model; not only your code (ie. django.contrib.auth.Group)

• handle list-editable ChangeList. (handle #11313)

• manage concurrency conflicts in admin’s actions

• can intercept changes performend out of the django app (ie using pgAdmin, phpMyAdmin, Toads) (using TriggerVersionField)

• can be disabled if needed (see disable_concurrency)

Links

Stable
Development
Project home page:	https://github.com/saxix/django-concurrency
Issue tracker:	https://github.com/saxix/django-concurrency/issues?sort
Download:	http://pypi.python.org/pypi/django-concurrency/
Documentation:	https://django-concurrency.readthedocs.org/en/latest/

_list-editable: https://django-concurrency.readthedocs.org/en/latest/admin.html#list-editable

[1]

http://en.wikipedia.org/wiki/Optimistic_concurrency_control