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
I think that could work, the idea would be that the .or() just combines the last set WHERE value and wraps it in parens with whatever comes next. If you do another .or() then it would just append that on again, so you can have whole chains of (... OR ... OR ...) statement fragments. I actually think that might work.
This would also give a viable path for #123 without having to implement anything that looks at every value passed into the in_* method
The text was updated successfully, but these errors were encountered:
Would something like this work:
Would result in a query like:
Or, maybe it could be even more clever and just infer:
I think that could work, the idea would be that the
.or()
just combines the last set WHERE value and wraps it in parens with whatever comes next. If you do another.or()
then it would just append that on again, so you can have whole chains of(... OR ... OR ...)
statement fragments. I actually think that might work.This would also give a viable path for #123 without having to implement anything that looks at every value passed into the
in_*
methodThe text was updated successfully, but these errors were encountered: