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

Allow disabling VCS findFreeName collision logic for copy

    XMLWordPrintable

    Details

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

      This can be set to disable free-name detection and let the database raise a constraint error in case of collisions IF THE CONSTRAINTS HAVE BEEN ADDED BY HAND:

      nuxeo.vcs.copy.findFreeName.disabled=true

      Show
      This can be set to disable free-name detection and let the database raise a constraint error in case of collisions IF THE CONSTRAINTS HAVE BEEN ADDED BY HAND: nuxeo.vcs.copy.findFreeName.disabled=true

      Description

      In some situations like a copy it's better to let the SQL database handle name collisions using database-level constraints (partial unique index on parentid + name).

      When this is activated, the code in SQLSession.findFreeName is actually harmful as it does a renaming with a time-based suffix instead of letting a constraint exception be raised and the higher-level layers deal with it.

      So it should be possible to disable the SQLSession.findFreeName logic for copy.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1 hour
                1h
                Remaining:
                Remaining Estimate - 1 hour
                1h
                Logged:
                Time Spent - Not Specified
                Not Specified