This PR is to fix #262 , which is caused by incorrect translation from PG sql dialect to T-SQL syntax when using LIMIT..OFFSET clause.
What is the current behavior?
The SQL with LIMIT..OFFSET clause will be deparsed to offset 0 rows fetch next .. rows only, but it needs ORDER BY clause to be presented in T-SQL while it is not necessary in Postgres.
What is the new behavior?
An error will happen when LIMIT..OFFSET clause is not with an ORDER BY clause.
What kind of change does this PR introduce?
This PR is to fix #262 , which is caused by incorrect translation from PG sql dialect to T-SQL syntax when using
LIMIT..OFFSETclause.What is the current behavior?
The SQL with
LIMIT..OFFSETclause will be deparsed tooffset 0 rows fetch next .. rows only, but it needsORDER BYclause to be presented in T-SQL while it is not necessary in Postgres.What is the new behavior?
An error will happen when
LIMIT..OFFSETclause is not with anORDER BYclause.Additional context
N/A