You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Though, we've supported parsing alternative orders of SELECT clauses before, e.g. Oracle's arbitrary ordering of CONNECT BY, START WITH, GROUP BY, HAVING.
The text was updated successfully, but these errors were encountered:
lukaseder
changed the title
Parser cannot combine FOR UPDATE with LIMIT clauses
Parser cannot parse reverse syntactic order of FOR UPDATE and LIMIT clauses
Nov 13, 2023
select*from t_book
for update skip locked
order by id
offset 1limit1
lukaseder
changed the title
Parser cannot parse reverse syntactic order of FOR UPDATE and LIMIT clauses
Parser cannot parse undocumented reverse syntactic order of FOR UPDATE and LIMIT clauses from PostgreSQL
Nov 13, 2023
This is valid in e.g. PostgreSQL:
But jOOQ cannot handle it, producing:
The correct syntax (even in PostgreSQL) should be:
According to the docs:
Though, we've supported parsing alternative orders of
SELECT
clauses before, e.g. Oracle's arbitrary ordering ofCONNECT BY
,START WITH
,GROUP BY
,HAVING
.The text was updated successfully, but these errors were encountered: