Skip to content

feat: support PostgreSQL 18 RETURNING OLD/NEW#2398

Merged
manticore-projects merged 1 commit intoJSQLParser:masterfrom
dengliming:support_return
Mar 5, 2026
Merged

feat: support PostgreSQL 18 RETURNING OLD/NEW#2398
manticore-projects merged 1 commit intoJSQLParser:masterfrom
dengliming:support_return

Conversation

@dengliming
Copy link
Contributor

Fixes #2327

@manticore-projects
Copy link
Contributor

Looks good, I will merge when tests pass.
Please pay attention to the Grammar, there are now lots of warning about ambiguity and missing LOOKAHEADs.

@dengliming
Copy link
Contributor Author

@manticore-projects Thanks. I'll check later.

@manticore-projects manticore-projects merged commit f47a8b3 into JSQLParser:master Mar 5, 2026
4 checks passed
@manticore-projects
Copy link
Contributor

@manticore-projects Thanks. I'll check later.

Reading from file /home/are/Documents/src/JSQLFormatter/JSQLParser/target/javacc-1772732167326/node/JSqlParserCC.jj . . .
Note: UNICODE_INPUT option is specified. Please make sure you create the parser/lexer using a Reader with the correct character encoding.
Warning: Choice conflict in [...] construct at line 2636, column 5.
         Expansion nested within construct and expansion following construct
         have common prefixes, one of which is: "WITH"
         Consider using a lookahead of 2 or more for nested expansion.
Warning: Choice conflict in [...] construct at line 7390, column 17.
         Expansion nested within construct and expansion following construct
         have common prefixes, one of which is: "ENCODING"
         Consider using a lookahead of 2 or more for nested expansion.
Warning: Choice conflict in [...] construct at line 7397, column 21.
         Expansion nested within construct and expansion following construct
         have common prefixes, one of which is: "ENCODING"
         Consider using a lookahead of 2 or more for nested expansion.
Warning: Choice conflict in (...)* construct at line 7676, column 9.
         Expansion nested within construct and expansion following construct
         have common prefixes, one of which is: ","
         Consider using a lookahead of 2 or more for nested expansion.
Warning: Choice conflict in [...] construct at line 8806, column 9.
         Expansion nested within construct and expansion following construct
         have common prefixes, one of which is: "PATH"
         Consider using a lookahead of 2 or more for nested expansion.
Warning: Choice conflict involving two expansions at
         line 8895, column 9 and line 8900, column 9 respectively.
         A common prefix is: <DATA_TYPE>
         Consider using a lookahead of 2 for earlier expansion.
Warning: Choice conflict in [...] construct at line 9834, column 5.
         Expansion nested within construct and expansion following construct
         have common prefixes, one of which is: "DESC"
         Consider using a lookahead of 2 or more for nested expansion.
Warning: Choice conflict in [...] construct at line 10297, column 21.
         Expansion nested within construct and expansion following construct
         have common prefixes, one of which is: "INDEX"
         Consider using a lookahead of 2 or more for nested expansion.
Warning: Choice conflict in [...] construct at line 10443, column 25.
         Expansion nested within construct and expansion following construct
         have common prefixes, one of which is: "INDEX"
         Consider using a lookahead of 2 or more for nested expansion.
Warning: Choice conflict in [...] construct at line 10537, column 37.
         Expansion nested within construct and expansion following construct
         have common prefixes, one of which is: "INDEX"
         Consider using a lookahead of 2 or more for nested expansion.
Warning: Choice conflict in [...] construct at line 10573, column 39.
         Expansion nested within construct and expansion following construct
         have common prefixes, one of which is: "INDEX"
         Consider using a lookahead of 2 or more for nested expansion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEATURE] PostgreSQL 18 : add support for RETURNING statement old and new values

2 participants