Please sync against latest development branch and resolve conflicts.
Thank you.

Any feedback please? I would like top close this otherwise.

Have this feature been merged into version 4. 7? Or is it planned to be added in which version?

You can test it online here.

SELECT datetime FROM tableA where anonymousid global in ( select distinct anonymousid from tableB)

I use this SQL to do testing and no error is reported

Greetings.

Your statement parses without any problem and you can try it online here.

Although you will need to take the latest JSQLParser Snapshot from http://manticore-projects.com/download/jsqlparser-4.7/JSQLParser-4.8-SNAPSHOT.jar

Note that this caused a regression: "global" is apparently matched everywhere, and it makes parsing things like select global.XWS_NAME from xwikistrings as global not possible anymore (ParseException: Encountered unexpected token: "as" "AS" at line 1, column 42).

It seems to be fixed by #2385 (and it indeed works fine in the online tool), but it's not released yet, and https://github.com/JSQLParser/JSqlParser/blob/master/src/site/sphinx/keywords.rst still lists "GLOBAL" as reserved, so I'm wondering if it was really on purpose. If perfectly valid queries like select global.XWS_NAME from xwikistrings as global are officially not supported anymore, it's going to be a blocker for us to upgrade...

@tmortagne: Your example works.

You can use the manticore artifacts:

<dependency>
    <groupId>com.manticore-projects.jsqlformatter</groupId>
    <artifactId>jsqlparser</artifactId>
    <version>[5.3.218,)</version>
</dependency>

GLOBAL is still a reserved keyword in the sense, that it will need to get quoted when using it as an identifier (at certain places).