Objective of database language
To clarify this objective, we need to first understand what the database does.
When it comes to database, it always...
For further actions, you may consider blocking this person and/or reporting abuse
I see that you dont like the SQL way to query the DB and prefer a procedural approach. Then you should look at the execution plan, not the SQL text. You try to read SQL as an English sentence with action verbs on physical structures. That doesn't work. The SQL code is a description of the expected result using a logical structure, without any hints on how it must be executed. Think of it as the user specification, not the developer implementation.
For example, you cannot guess the execution logic from SQL statement like you did:
This is wrong except if
Tis a table with no index onxwhich would be a mistake. This SQL only defines the result as the last 10 rows byx. Why do you think it has to read all and eliminate later?