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
{{ message }}
This repository has been archived by the owner on Mar 30, 2022. It is now read-only.
I'm pretty sure this is standard behavior, see: #272 for examples of expected behavior re: subqueries and Rails.
If you need "id" IN (1,2), I think I would just .to_a.map &:id ( or perhaps just to_a would give you what you want, maybe the magic is in recognizing that you passed an CollectionProxy ).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've noticed that in my updated app, subqueries are generated when I supply a relation in a regular where():
This introduces a subquery instead of standard Rails array of ids:
IMO, Squeel should only work this kind of magic inside a where{} block.
The text was updated successfully, but these errors were encountered: