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
After looking into this some more, it does seem like JPA 2.1 does support JOIN...ON... queries, so it is feasible to support this. It's possible that if you define an entity relationship, then the JPA provider might also be able to make use of this optimization automatically without needing to explicitly use JOIN...ON... in a query.
I don't really have the time to work on major features for Jinq though, so unless the performance issue is so bad that it's absolutely required, then I probably won't be able to work on this.
I hope join supports custom on conditions, because it can get faster speed than where conditions.
The text was updated successfully, but these errors were encountered: