> That's SQL, my friend. OFFSET first, then LIMIT. Irrespective of the
> order
> in the query statement. It is what it is. SQL doesn't depend on LINQ for
> its semantics.
SQL requires strong order of all cases. Postgres syntax help about OFFSET /
LIMIT also
describes only single order.
Actually Postgres allows order of OFFSET / LIMIT clauses swapped without any
error.
Why Postgres does not throw error when SELECT ... LIMIT ... OFFSET is used ?
That's not sql and should cause error.
Andrus.
