Fix one-to-many relation create/edit with SQLAlchemy#707
Open
tmshlvck wants to merge 1 commit into
Open
Conversation
One-to-many relations do not automatically fill the relation_id foreign key, which causes 422 errors propagation with no save to the DB By this patch we bind the foreign key column with the relation "virutal" column in SQLModel / SQLAlchemy - the name of the foreign key has to be "<relation>_id", which corresponds with the existing documentation.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
One-to-many relations do not automatically fill the relation_id foreign key, which causes 422 errors propagation with no save to the DB
By this patch we bind the foreign key column with the relation "virutal" column in SQLModel / SQLAlchemy - the name of the foreign key has to be "_id", which corresponds with the existing documentation.
This closes #485 and probably two related/duplicate issues.