To get what you expect from the Lukas solution (as of November 1, 2011), luck was a success . In RDBMS, by definition, there is no “natural order” . You depend on implementation details that are subject to change with the new version without notice. Or reset / restore can change this order. It may even change due to blue when the db statistics change and the query scheduler selects a different plan that leads to a different row order.
the correct way to get the rows "last n" is to have a timestamp or sequence ORDER BYcolumn and that column. Each RDBMS that you can think of has ORDER BY, therefore, it is "general" as you receive it.
I :
ORDER BY , .
Lukas LIMIT, - (, SQL Server TOP n LIMIT), ORDER BY .
, , , SQL, - , . MySQL, , .