@sgrif Is there any reason ActiveRecord predicate builder doesn't work with Set's by default? Could even just use ArrayHandler.
-
-
Replying to @BrianVanLoo
@BrianVanLoo Because the argument for `Set` is the argument for any `Enumerable`, which isn't something we want to do.1 reply 0 retweets 0 likes -
Replying to @BrianVanLoo
@BrianVanLoo It'll depend on how that type casts unrecognized values. If it were a string column it would have called `.to_s` on it.1 reply 0 retweets 0 likes -
Replying to @sgrif
@sgrif Ah. Kind of even more surprising to me. Any chance you'd discuss why these things work this way on@_bikeshed?1 reply 0 retweets 0 likes -
Replying to @BrianVanLoo
@BrianVanLoo Why we coerce values? Or something more specific?1 reply 0 retweets 0 likes -
Replying to @BrianVanLoo
@sgrif As promised here is something more long-form describing why this seems surprising: https://gist.github.com/ratdaddy/73472a1c2ee5ae88c94b …7 replies 0 retweets 0 likes
@BrianVanLoo As for why the query ends up being what it is, since Set isn't treated specially, we assume you mean equality comparison 2/?
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.