Description

donshop11

opened on Aug 5, 2015

Issue body actions

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

1. fudianchn

   added a commit that references this issue on Aug 15, 2026

   feat: support SQL Server OPTION query hints (JSQLParser#161)

   3bca3dc
2. fudianchn commented on Aug 15, 2026

   

   fudianchn

   on Aug 15, 2026

   Contributor

   More actions

   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 of SELECT (including after set operations and FOR XML), UPDATE and DELETE parses into a new OptionClause holding OptionHints (keyword name + optional value or argument list). The statement from this issue parses into PlainSelect with MAXRECURSION 2 accessible from the AST and deparse round-trips unchanged; all query hint forms currently documented by Microsoft parse as well, and option stays a non-reserved keyword usable as column and table name.
3. manticore-projects

   added a commit that references this issue on Aug 16, 2026

   feat: support SQL Server OPTION query hints (#161) (#2472)

   138947d
4. manticore-projects

   closed this as completedin #2472on Aug 16, 2026

Issue actions