Here’s a full list of all available settings, in alphabetical order, and their default values.
Each entry MUST have the prefix
CONCURRENCY_ when used in your settings.py
Handler invoked when a conflict is raised. The default implementation
Can be used to display the two version of the record and let the user to force the update or merge the values.
Class used to sign the version numbers.
Handler to intercept
The default implementation (concurrency.views.conflict) renders
while passing into the context the object that is going to be saved (
- If false do not automatically create triggers, you can create them using triggers management command
- management command or manually using your DB client.
Determines whether a default version number is ignored or used in a concurrency check. While this
configuration defaults to True for backwards compatibility, this setting can cause omitted version
numbers to pass concurrency checks. New implementations are recommended to set this to
For security reasons, starting from version 1.5, default value will be
Used by admin’s integrations to handle
Do not save conflicting records, continue and save all non-conflicting records,
show a message to the user
Used by admin’s integations to handle
Stop at the first conflict and raise
Note that if you want to use
based conflict management you must set this flag.