Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-22421

Database-level integrity constraints for PostgreSQL

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 9.2
    • Component/s: Core VCS
    • Backlog priority:
      500
    • Impact type:
      Configuration Change
    • Upgrade notes:
      Hide

      On VCS the repository configuration can now contain
      <childNameUniqueConstraintEnabled>true</childNameUniqueConstraintEnabled>
      This is available for PostgreSQL, and enabled by default.

      Show
      On VCS the repository configuration can now contain <childNameUniqueConstraintEnabled>true</childNameUniqueConstraintEnabled> This is available for PostgreSQL, and enabled by default.
    • Sprint:
      nxFG 9.2.6
    • Story Points:
      5

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day, 2 hours
                  1d 2h