FOUND_ROWS

Returns the number of rows when using commands that return a resultset, such as SELECT, DESC, and SHOW.

Syntax

FOUND_ROWS()

Arguments

  • None

Return Type

int

Examples

SHOW TABLES;
+--------------+
| Tables_in_db |
+--------------+
| testdata     |
+--------------+
SELECT FOUND_ROWS();
+--------------+
| FOUND_ROWS() |
+--------------+
|            1 |
+--------------+
SELECT ID FROM neighborhoods LIMIT 2;
+------+
| id   |
+------+
|    1 |
|    3 |
+------+
SELECT FOUND_ROWS();
+--------------+
| FOUND_ROWS() |
+--------------+
|            2 |
+--------------+
SELECT * FROM testdata;
+----------+
| Results  |
+----------+
|        1 |
|        2 |
|        3 |
|        4 |
|        5 |
+----------+ 
SELECT FOUND_ROWS;
+--------------+
| FOUND_ROWS() |
+--------------+
|            5 |
+--------------+
DESC testdata;
+-------+---------+------+------+---------+-----------+
| Field  | Type       | Null | Key  | Default | Extra |
+-------+-------------+------+------+---------+-------+
| id     | int(10)    | NO   |      | NULL    |       |
+--------+------------+------+------+---------+-------+
| name   | varchar(64)| NO   |      | NULL    |       |
+--------+------------+------+------+---------+-------+        
| amount | int(10)    | NO   |      | NULL    |       |
+-------+---------+------+------+---------+-----------+
SELECT FOUND_ROWS;
+--------------+
| FOUND_ROWS() |
+--------------+
|            1 |
+--------------+

Note

Please note, there can be an incorrect result given when running a query using LIMIT with an offset. See the following example:

CREATE TABLE t1(a BIGINT PRIMARY KEY AUTO_INCREMENT, b INT);
INSERT random integers into t1 so total row count is greater than LIMIT argument.
SELECT COUNT(*) FROM t1 GROUP BY a ORDER BY a LIMIT 5,10;
+----------+
| COUNT(*) |
+----------+
|        1 |
|        1 |
| 1 |
|        1 |
|        1 |
|        1 |
|        1 |
|        1 |
|        1 |
|        1 |
+----------+
10 rows in set (0.03 sec)
SELECT FOUND_ROWS(); -- the result should be 10
+--------------+
| FOUND_ROWS() |
+--------------+
|           15 |
+--------------+
1 row in set (0.00 sec)

Last modified: April 4, 2023

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined
  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined
  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
    --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
    --bundle undefined \
    --new-bundle-format -
    Verified OK