In scenarios where it's not possible to have an application-level lock to ensure uniqueness of document name creation in a parent, or uniqueness of a complex property list element, or non-parallelism of list extension, in some SQL databases it's possible to have additional database-level constraints that would raise a ConcurrentUpdateException if this situation arises.
This comes with a performance impact, so must be conditioned by a flag that can be removed for users that don't need it.
When using PostgreSQL, stricter database-level checks are now enabled to prevent rare document name collisions due to concurrent writes.
- is related to
-
NXP-22724 Database-level integrity constraints on simple lists for PostgreSQL
- Resolved
-
NXP-28406 Handle duplicates with MongoDB
- Resolved
-
NXP-22959 Add a mode to prevent duplicate documents
- Open
- is required by
-
NXP-26825 Handle soft-delete enablement with child name unique constraint
- Resolved
-
NXP-23236 AgendaOperationsTest failure on PostgreSQL
- Resolved
-
NXP-22826 Better concurrency for FileManagerService name creation
- Open
-
NXDRIVE-926 Automatically retry on 409 (Conflict)
- Resolved