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

HCK-8237: field single PK and UK should be mutually exclusive #122

Merged
merged 4 commits into from
Oct 4, 2024

Conversation

taras-dubyk
Copy link
Contributor

@taras-dubyk taras-dubyk commented Oct 2, 2024

Sub-taskHCK-8237 Single PK should not be also declared as single UK (mutually exclusive) - config only?

Content

In this PR:

  • I added hiding unique field property if it's already a single primary and vice versa.
  • added an adapter to remove a single "unique" property in case a field is a single PK and a single UK simultaneously. In another case, both properties would be hidden.
  • allowed for a field to be checked as unique in case it is already a part of a composite primary key.

Copy link

sonarcloud bot commented Oct 3, 2024

@taras-dubyk taras-dubyk self-assigned this Oct 3, 2024
@taras-dubyk taras-dubyk marked this pull request as ready for review October 3, 2024 14:01
@VitaliiBedletskyi VitaliiBedletskyi enabled auto-merge (squash) October 3, 2024 15:08
@taras-dubyk taras-dubyk merged commit d9b50d7 into develop Oct 4, 2024
7 of 8 checks passed
@taras-dubyk taras-dubyk deleted the fix/HCK-8237-single-pk-uk-mutually-exclusive branch October 4, 2024 11:23
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.

2 participants