-
Notifications
You must be signed in to change notification settings - Fork 196
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
Feature: Remove condition for joins. #17
Comments
@zekefast could you show me an example of how you think this should work? or how would you like to use it? |
I also need this feature. |
I'm having a similar problem, except with #includes instead of #joins. Here's an example:
Running the code above results in the following queries being executed:
This returns incorrect results since deleted resources are being filtered out, despite the belongs_to association having specified with_deleted: true This was a known issue in an older version of this gem: This was the pull request that fixed it: I'll submit a new pull request. |
@pelargir I see, thank you! |
I am having the same problem as @pelargir with the |
I'll see if we can get this cleaned up and merged before the final release <3 |
I've merged #37 so closing this ticket. |
It would be awesome if you would add ability to unscope joins or let unscoped affect joined associations as well.
Now there is no way to include deleted associations into joined conditions. It always adds something like
"rabbits"."deleted_at" IS NULL
to theFROM carrots INNER JOIN rabbits ON rabbits.id = carrots.rabbit_id
.The text was updated successfully, but these errors were encountered: