Description\n-----------\n\nUse the LIMIT clause to restrict the number of returned rows. When you use a single integer _n_ with LIMIT, the first _n_ rows will be returned. Use the ORDER BY clause to control which rows come first. You can also select a number of rows after an offset using either of the following:\n\n``sql\nLIMIT offset, row_count\nLIMIT row_count OFFSET offset\n`\n\nWhen you provide an offset _m_ with a limit _n_, the first _m_ rows will be ignored, and the following _n_ rows will be returned.\n\nExecuting an UPDATE with the LIMIT clause is not safe for replication. LIMIT 0 is an exception to this rule (see MDEV-6170).\n\nThere is a LIMIT ROWS EXAMINED optimization which provides the means to terminate the execution of SELECT statements which examine too many rows, and thus use too many resources. See LIMIT ROWS EXAMINED.\n\nMulti-Table Updates\n\nIt is possible to use LIMIT (or ORDER BY) in a multi-table UPDATE statement.\n\nIt is not possible to use LIMIT (or ORDER BY) in a multi-table UPDATE statement.\n\nGROUP_CONCAT\n\nIt is possible to use LIMIT with GROUP_CONCAT().\n\nIt is not possible to use LIMIT` with GROUP_CONCAT().\n\nExamples\n--------\n\nCREATE TABLE members (name VARCHAR(20));\nINSERT INTO members VALUES('Jagdish'),('Kenny'),('Rokurou'),('Immaculada');\n\nSELECT * FROM members;\n+------------+\n| name       |\n+------------+\n| Jagdish    |\n| Kenny      |\n| Rokurou    |\n| Immaculada |\n+------------+\n\nURL: https://mariadb.com/docs/server/reference/sql-statements/data-manipulation/selecting-data/limit