Skip to main content
https://secure.travis-ci.org/gavinwahl/django-optimistic-lock.png?branch=master

Implements an offline optimistic lock [1] for Django models.

Usage

Add a VersionField and inherit from VersionedMixin.

from ool import VersionField, VersionedMixin

class MyModel(VersionedMixin, models.Model):
    version = VersionField()

Whenever MyModel is saved, the version will be checked to ensure the instance has not changed since it was last fetched. If there is a conflict, a ConcurrentUpdate exception will be raised.

Implementation

A VersionField is just an integer that increments itself every time its model is saved. VersionedMixin overrides _do_update (which is called by save to actually do the update) to add an extra condition to the update query – that the version in the database is the same as the model’s version. If they match, there have been no concurrent modifications. If they don’t match, the UPDATE statement will not update any rows, and we know that someone else saved first.

This produces SQL that looks something like:

UPDATE mymodel SET version = version + 1, ... WHERE id = %s AND version = %s

When no rows were updated, we know someone else won and we need to raise a ConcurrentUpdate.

Comparison to django-concurrency

django-concurrency before version 0.7 used SELECT FOR UPDATE to implement the version checking. I wanted to avoid database-level locking, so django-optimistic-lock adds a version filter to the update statement, as described by Martin Fowler [1].

Additionally, ool takes a more minimalistic approach than django-concurrency by only doing one thing – optimistic locking – without any monkey-patching, middleware, settings variables, admin classes, or form fields. django-concurrency would probably make more sense if you’re looking for something that will attempt to accommodate every situation out of the box. Use ool if you just want a straightforward model implementation and need to handle the UI and surrounding architecture yourself.

Running the tests

make test

Release files for django-optimistic-lock 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for django-optimistic-lock 1.0.0
File Size Uploaded
django-optimistic-lock-1.0.0.tar.gz 8.0 kB Details

Release files / django-optimistic-lock-1.0.0.tar.gz

Download URL django-optimistic-lock-1.0.0.tar.gz
Size 8.0 kB
Tags Source
SHA-256 checksum
How to use checksums
dcc9cdc2219e6ec36757457d1ee9e55b2ec851d75308ad1080c1c2f00951cac8
BLAKE2b-256 checksum
How to use checksums
85720131f985549f9ef656dee4888dc193f37c12b2a461d04e3b6afd34c377f8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.12.1 pkginfo/1.4.2 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.6+

Release history Release notifications | RSS feed

This release

1.0.0 This release

1 release file

0.1

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page