-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Scopes are not processed when evaluating Join conditions #7076
Comments
The issue has been automatically marked as stale as it missing playground pull request link, which is important to help others understand your issue effectively and make sure the issue hasn't been fixed on latest master, checkout https://github.com/go-gorm/playground for details. it will be closed in 30 days if no further activity occurs. if you are asking question, please use the |
Added playground pull request go-gorm/playground#743 |
Playground Pull Request Link
go-gorm/playground#743
Description
When using Joins/InnerJoins, there is an inconsistency about how the join clause is processed.
My application uses a number of preprepared filters, including some generated dynamically.
When used as Scopes() for normal queries, they work fine, but when they are used as a clause in a Join() or InnerJoin() they are ignored
Note the "AND Group.id = 2" - this is as expected.
In this case the parameter is checked, and isnt a simple "Where" clause, so it is ignored.
If "chainable_api.go" included a call to
db.executeScopes()
before checkingThis would work.
(Ps, I'm new to gorm playground, and I couldn't get past the
gorm.io/gen/examples/dal: cannot find module providing package gorm.io/gen/examples/dal
error)Go playground test output
Sample Code
Edit: formatting
The text was updated successfully, but these errors were encountered: