-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to parse ORACLE LISTAGG-Function in combination with OVER-Clause #1652
Comments
|
Hi @wumpz Thank you for your reply. Unfortunately your suggestion is not feasible. According to Oracle's documentation (https://docs.oracle.com/cd/E11882_01/server.112/e41084/functions089.htm#SQLRF30030) the WITHIN GROUP clause is not optional when using LISTAGG. The execution results in an ORA-02000 when the WITHING GROUP clause is omitted. |
Greetings, thank your for reporting. |
@andghe unfortunately you are right: http://sqlfiddle.com/#!4/c6069c/4/0. Sorry I missed that. |
fixes issue JSQLParser#1652 fixes 3 more Special Oracle Tests
* fix: add missing public Getter Add public Getter for `updateSets` Fixes #1630 * feat: LISTAGG() with OVER() clause fixes issue #1652 fixes 3 more Special Oracle Tests * fix: White-list CURRENT_DATE and CURRENT_TIMESTAMP tokens allows CURRENT_DATE(3) and CURRENT_TIMESTAMP(3) as regular functions fixes #1507 fixes #1607 * feat: Deparser for Expression Lists Visit each Expression of a List instead ExpressionList.toString() fixes #1608 * fix: Lookahead needed
Hi
The parser (version 4.5) reports
while parsing the following statement (reduced to the minimum with sample data included):
This is fine ORACLE-Sql (see https://docs.oracle.com/cd/E11882_01/server.112/e41084/functions089.htm#SQLRF30030) and returns something like
I was able to reduce the Problem to the OVER-Clause, as the following (semantically different) snippet is parseable:
Fix/Workaround would be appreciated.
The text was updated successfully, but these errors were encountered: