🐛 FIX: sqlalchemy v2 API warning #5177
Merged
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
This commit fixes a warning that is generated by the sqlalchemy: SAWarning: relationship 'DbLink.input' will copy column db_dbnode.id to column db_dblink.input_id, which conflicts with relationship(s): 'DbNode.inputs_q' (copies db_dbnode.id to db_dblink.input_id), 'DbNode.outputs_q' (copies db_dbnode.id to db_dblink.input_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="inputs_q,outputs_q"' to the 'DbLink.input' relationship. Note a similar fix was made in aldjemy/aldjemy#199
Codecov Report
@@ Coverage Diff @@
## develop #5177 +/- ##
========================================
Coverage 80.93% 80.93%
========================================
Files 536 536
Lines 37056 37056
========================================
Hits 29987 29987
Misses 7069 7069
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
This commit fixes a warning that is generated by the sqlalchemy:
SAWarning: relationship 'DbLink.input' will copy column db_dbnode.id to column db_dblink.input_id, which conflicts with relationship(s): 'DbNode.inputs_q' (copies db_dbnode.id to db_dblink.input_id), 'DbNode.outputs_q' (copies db_dbnode.id to db_dblink.input_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="inputs_q,outputs_q"' to the 'DbLink.input' relationship.
Note a similar fix was made in aldjemy/aldjemy#199