Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enh add UUID validaton/enforcement for contentcontainer, file, space and user #6690

Closed

Conversation

martin-rueegg
Copy link
Contributor

@martin-rueegg martin-rueegg commented Dec 1, 2023

This PR enforces a valid UUID for guid column for contentcontainer, file, space and user. 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?

  • Feature

Does this PR introduce a breaking change?

  • Yes

If yes, please describe the impact and migration path for existing applications:

guid column for contentcontainer, file, space and user are now enforced to be valid UUIDs.

The PR fulfills these requirements

  • It's submitted to the develop branch
  • When resolving a specific issue, it's referenced in the PR's description (e.g. Fix #xxx[,#xxx], where "xxx" is the Github issue number)
  • All tests are passing
  • New/updated tests are included
  • Changelog was modified
  • A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

@martin-rueegg
Copy link
Contributor Author

Sorry, duplicate of

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant