Postgres: allow foreign key column without unique constraint #131
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
tyt2y3
reviewed
Apr 29, 2024
tests/live/postgres/src/main.rs
Outdated
Comment on lines
58
to
59
| create_table1(), | ||
| create_table2(), |
There was a problem hiding this comment.
Thanks. Can we have a slightly more descriptive name, like fkey_parent_table / fkey_child_table?
tyt2y3
approved these changes
May 5, 2024
🎉 Released In 0.15.0 🎉Thank you everyone for the contribution! |
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.
PR Info
referential_key_table_nameempty for some schemas (panic on Option::unwrap on None during migration) since sea-schema 0.14.2 #130Bug Fixes