Fixes check for primary key name in Postgres #15407
Merged
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.
Description
Hey! I’m running into an issue where this migration can’t be run on a Postgres database, because the primary key can’t be found.
This PR is a bit of guess, but I’m wondering if this PR is another valid way to get the key? The database I’m using started life as a Craft 2 project in MySQL, and at some point went through this migration process to Postgres, so it’s possible this is a project-specific issue.
In any case, the constraint had an entirely different name in this DB, and once I made this change the migration ran successfully.