Apparently at least butler query-data-ids calls the count method on a query result object without telling it what to do when counting the results would have to be implemented by iterating over all results and then throwing them away, resulting in an error that uses shouldn't have to see in a high-level call like this:

https://lsstc.slack.com/archives/C01FBUGM2CV/p1682469497459669

This bug was introduced in DM-31725, but the behavior before was not great either, as it would have just silently run the query twice and thrown away the results from the first call after counting them.