Align Postgres tables/indexes/constraints with Django #1697
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
danlamanna
reviewed
Oct 6, 2023
danlamanna
approved these changes
Oct 6, 2023
danlamanna
approved these changes
Oct 12, 2023
jjnesbitt
added
patch
|
🚀 PR was released in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While working on a separate PR, I encountered an error when trying to update a constraint on the
ZarrArchivemodel, which led me to realize that there was a mismatch between what Django thinks the name of these constraints are, and what they actually are in Postgres. It appears the renaming of these constraints slipped through the cracks in #1256, specifically the*-consistent-checksum-statusand*-unique-nameconstraints.This PR aligns those names with reality in Postgres, as well as renames the tables and all other indexes/constraints, to be consistent with what we expect.