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.

Sign up for GitHub

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

Jump to bottom

fix(database): getSchemas filters, declared schema collectionName uniqueness constraint #368

Merged
merged 2 commits into from
Oct 5, 2022
Merged

fix(database): getSchemas filters, declared schema collectionName uniqueness constraint #368

merged 2 commits into from
Oct 5, 2022

Conversation

kon14
Copy link
Contributor

@kon14 kon14 commented Oct 5, 2022

Fixes getSchemas()'s owner and enabled filters.
Introduces a db level uniqueness constraint on DeclaredSchema's collectionName field.

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update
  • Refactor
  • Build-related changes
  • Other (please describe)

Does this PR introduce a breaking change?

  • Yes
  • No

The PR fulfills these requirements:

  • It's submitted to the main branch
  • When resolving a specific issue, it's referenced in the PR's description (e.g. fix #xxx, where "xxx" is the issue number)

@kkopanidis kkopanidis merged commit 245fe13 into main Oct 5, 2022
@kkopanidis kkopanidis deleted the db-unique branch October 5, 2022 12:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@kkopanidis kkopanidis kkopanidis approved these changes

@ChrisPdgn ChrisPdgn Awaiting requested review from ChrisPdgn

@SotiriaSte SotiriaSte Awaiting requested review from SotiriaSte

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@kon14 @kkopanidis