-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update 'users' unique constraints #469
Conversation
changes: | ||
- addUniqueConstraint: | ||
columnNames: subject_id, project_id | ||
constraintName: UK_subject_project |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can maybe make this a bit more unique to avoid clashes (like adding timestamp at the end or a random string)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes made the changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Btw did we find this happening in our deployments too? given that we check for this in the service method.
Yeah this is happening in our deployment. And only on the |
users
entity and table unique constraintssubject_id
andproject_id
columns uniqueSolves #468