Enh add UUID validaton/enforcement for contentcontainer
, file
, space
and user
#6690
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR enforces a valid UUID for
guid
column forcontentcontainer
,file
,space
anduser
. Currently arbitrary and non-unique string values up to 45 chars are allowed. This can lead to potential conflicts.PR Admin
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
If yes, please describe the impact and migration path for existing applications:
guid
column forcontentcontainer
,file
,space
anduser
are now enforced to be valid UUIDs.The PR fulfills these requirements
develop
branchFix #xxx[,#xxx]
, where "xxx" is the Github issue number)