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
As far as I can tell, count() returns meaningless results when the query contains a limit or offset (neither the total, nor the limited, number of results).
As per the docs, "count() will automatically default to wrapped_count() in the event the query is distinct or has a grouping".
I think that's nice; exactly what you want in the case of distinct or group by. Wouldn't it make sense for it to do the same if the query has a limit or offset?
If not, what's the rationale behind that?
The text was updated successfully, but these errors were encountered:
Additionally, I think count() should have a clear_limit parameter which it passes through to wrapped_count() -- I'm mentioning this as a comment here, not a separate issue, because it would only make sense if count deferred to wrapped_count for limits and offsets.
I think that's nice; exactly what you want in the case of distinct or group by. Wouldn't it make sense for it to do the same if the query has a limit or offset?
As far as I can tell, count() returns meaningless results when the query contains a limit or offset (neither the total, nor the limited, number of results).
As per the docs, "count() will automatically default to wrapped_count() in the event the query is distinct or has a grouping".
I think that's nice; exactly what you want in the case of distinct or group by. Wouldn't it make sense for it to do the same if the query has a limit or offset?
If not, what's the rationale behind that?
The text was updated successfully, but these errors were encountered: