Repository navigation
add support for SQL Server Query Hints #161
Description
the following query does not parse:
SELECT CustomerID, PersonID, StoreID
FROM cte
OPTION (MAXRECURSION 2);
see description here:
https://msdn.microsoft.com/en-us/library/ms181714.aspx
The value inside the OPTION is not that important to parse, it is more important not to fail parsing this kind of statements.
Activity
feat: support SQL Server OPTION query hints (JSQLParser#161)
fudianchn commentedon Aug 15, 2026
Root cause: the grammar has no production for the T-SQL
OPTION (...)query hint clause, so any statement carrying one fails to parse.PR #2472 adds it:
OPTION (...)at the end ofSELECT(including after set operations andFOR XML),UPDATEandDELETEparses into a newOptionClauseholdingOptionHints (keyword name + optional value or argument list). The statement from this issue parses intoPlainSelectwithMAXRECURSION 2accessible from the AST and deparse round-trips unchanged; all query hint forms currently documented by Microsoft parse as well, andoptionstays a non-reserved keyword usable as column and table name.feat: support SQL Server OPTION query hints (#161) (#2472)