Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix sqlalchemy overlaping relationship warning on startup #27

Merged
merged 1 commit into from
Jun 19, 2023

Conversation

jakubman1
Copy link
Contributor

The backref attribute is considered legacy in current versions of SQLAlchemy and should be replaced with back_populates with explicit relationship definition - see https://docs.sqlalchemy.org/en/20/orm/backref.html.

This PR fixes the "relationship X will copy column Q to column P, which conflicts with relationship(s): Y" warnings on ExaFS startup by removing the duplicate relationship caused by combining backref attribute with explicit relationship definition on API key model.

The backref attribute is considered legacy in current versions
of SQLAlchemy and should be replaced with back_populates with
explicit relationship definition [1].

This commit fixes the "relationship X will copy column Q to column P,
which conflicts with relationship(s): Y" warnings on ExaFS startup
by removing the duplicate relationship caused by combining
backref attribute with explicit relationship definition on API key model.

[1] https://docs.sqlalchemy.org/en/20/orm/backref.html
@jirivrany jirivrany merged commit 49dee92 into CESNET:develop Jun 19, 2023
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants