Allow difference for `and`/`or` unless other values are set explicitly
I often hit the inconvenience (recently in #39558). `and`/`or` are focused to combine where-like clauses, so we often use one-time relation which has only where clause. But if the receiver has values other than where clause (e.g. `order`, `select`, `includes`, etc), `and`/`or` will raise structurally incompatible error. Since it is harder to predict the receiver has which values other than where clause before doing `and`/`or`, that restriction is a little annoying to me. So I'd like to relax that restriction, at least unless other values are set explicitly for multiple values.
Showing
想要评论请 注册 或 登录