GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — feat: support PostgreSQL 18 RETURNING OLD/NEW by dengliming · Pull Request #2398 · JSQLParser/JSqlParser

Conversation

@dengliming

@dengliming dengliming commented Mar 5, 2026

Copy link
Copy Markdown
Contributor

Fixes #2327

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@dengliming
feat: support PostgreSQL 18 RETURNING OLD/NEW
f0d66b3
@manticore-projects

manticore-projects commented Mar 5, 2026

Copy link
Copy Markdown
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.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@dengliming

dengliming commented Mar 5, 2026

Copy link
Copy Markdown
Contributor Author

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

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

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

Uh oh!

There was an error while loading. Please reload this page.

@manticore-projects

manticore-projects commented Mar 5, 2026

Copy link
Copy Markdown
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.
dengliming reacted with thumbs up emoji
All reactions
  • 👍 1 reaction

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@dengliming dengliming mentioned this pull request Mar 5, 2026
fix(parser): resolve grammar LOOKAHEAD conflicts #2399
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

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

Uh oh!

There was an error while loading. Please reload this page.

2 participants

@dengliming @manticore-projects
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.