You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well, in "pure" SQL, navigability is not a factor and foreign keys are added to the class where it makes sense based on the cardinality. Should this be really different in SQLAlchemy?
We could update the generator to remove the relationship (last line in the code above) when the navigability is False. This would keep the Foreign Key in the Pet table, ensuring it’s still associated with a Person, but Pet wouldn’t be able to directly access Person. This is possible in SQLAlchemy
Describe the bug
The SQLAlchemy generator transform unidirectional associations to bidirectional associations
To Reproduce
Expected behavior
No back population nor inverse relation created for this association
Screenshots
The text was updated successfully, but these errors were encountered: