MySQL COUNT with LIMIT

70,070

This is actually how your query works and is a normal behaviour. Using LIMIT you will not limit the count or sum but only the returned rows. So your query will return n rows as stated in your LIMIT clause. And since your query actually returns only one row, applying a (non-zero) limit has no effect on the results.

However, your second query will work as expected and is an established way of solving this problem.

Share:
70,070
Lee
Author by

Lee

Updated on July 05, 2022

Comments

  • Lee
    Lee almost 2 years

    What I want to do is SUM a column, but also COUNT the number of rows it is summing, with a limit of no more than 5 rows. So my query is:

    SELECT COUNT(*), SUM(score) FROM answers WHERE user=1 LIMIT 5
    

    What I expected back was a COUNT(*) up to 5 (I cant just assume it will always be 5 in my code logic as it could have less than 5 answers), with a sum of the score of the up to 5 rows.

    Instead what I seem to get back is the total number of matching rows (where user is 1) as the count, and the sum of the score for those rows. The numbers don't change whether I put LIMIT 1 or LIMIT 5 or even LIMIT 50.

    What I believe will work in this situation is this instead

    SELECT COUNT(*), SUM(score) FROM (SELECT * FROM answers WHERE user=1 LIMIT 5) AS a
    

    But that seems a little convoluted for such a simple query, and as it's in a high traffic script, I want it to be as performant as possible.

    Am I missing something? I did find this bug report from a few years back which seems to be related to this "problem", but I'm assuming it's not actually a bug?

    • ta.speot.is
      ta.speot.is about 11 years
      LIMIT 5 will return at most 5 rows. SELECT COUNT(*), SUM(score) FROM answers will return 1 row. 1 < 5. You have it correct in the second query.
    • Lee
      Lee about 11 years
      Yep @ta.speot.is , think i just needed someone to verify i wasn't doing something stupid. Could have swore there was a simpler query to do what i needed, but obviously not.
    • Bogdan Gusiev
      Bogdan Gusiev almost 9 years
      using select 1 instead of select * in nested query can theoretically lead to less memory usage
  • Lee
    Lee about 11 years
    I'll accept your answer once the SO timer lets me. But you're right, think i just needed someone else to explain it too me so i knew i wasn't doing something silly. The second query does work, and seems to be the only way to do it.