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
Thanks @joshuaclayton for taking the time to report the issue. I can confirm that seaography does not take in mind the on_condition property. We will take care of the issue when we will update to sea-orm version 0.12
Description
With an
on_condition
within an entity relationship, the corresponding SQL query doesn't incorporate that scope.Imagine a simple structure where a BlogPost has a published boolean and an FK to Author. By defining two relationships:
I would expect accessing
publishedPosts
to apply theon_condition
:However, the
on_condition
is not applied.Expected Behavior
I expect the additional scoping from the
on_condition
to apply when the GraphQL query is run.Actual Behavior
The foreign key is honored but not the additional
on_condition
.Reproduces How Often
Yes.
Versions
Latest Seaography.
Additional Information
I think I've narrowed down the location where the
on_condition
should be applied:seaography/src/query/entity_object_relation.rs
Line 123 in 4eeaaa5
The text was updated successfully, but these errors were encountered: