-
Notifications
You must be signed in to change notification settings - Fork 0
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
Schema: name all constraints, not just PKs #226
Conversation
31869f0
to
5f0c38b
Compare
Fresh schema dump matches upgraded schema dump. incident_contact's CONSTRAINTs are already named properly. |
5f0c38b
to
65aeacf
Compare
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.
- You use a prefix for everything expect for checks where you use a
_check
suffix. Incremental Configuration Updates #191 started usingck_
as a prefix, it's not yet merged, but it should stay consistent, so I'd prefer a prefix, I'd be fine with bothck_*
andcheck_*
. key_
doesn't sound like a good prefix for unique constraints to me. Primary and foreign keys are also keys and in MySQL/MariaDB, key actually means index (from https://dev.mysql.com/doc/refman/8.4/en/create-table.html: "KEY is normally a synonym for INDEX."). If we want to keep everything abbreviated,uk_*
(unique key) might be an option, otherwise simplyunique_*
would also do.
65aeacf
to
dca1109
Compare
dca1109
to
b9b814c
Compare
b9b814c
to
3fd4572
Compare
38da15f
to
bed578b
Compare
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.
Looks fine for me now from looking at the changes. If the others are happy as well, mark their comments as resolved, I'd apply it to my test setup, spin it up for a quick test and give an actual approval.
The changes I requested were addressed, so this doesn't have to show up as changes requested anymore. Final approval will follow later, see #226 (review)
bed578b
to
96561ec
Compare
96561ec
to
27aea85
Compare
27aea85
to
bcf4c31
Compare
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.
LFTM!
fixes #202