-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[feat] Support for JSON_TABLE #2328
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
base: master
Are you sure you want to change the base?
Conversation
manticore-projects
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work and I do appreciate your effort and dedication. Thank you much!
A few small concerns though, nothing severe just the normal German nit-picking.
Kudos and cheers!
| | <#TYPE_REAL: "REAL" | "FLOAT4" | "FLOAT"> | ||
| | <#TYPE_DOUBLE: "DOUBLE" | "PRECISION" | "FLOAT8" | "FLOAT64"> | ||
| | <#TYPE_VARCHAR: "NVARCHAR" | "VARCHAR" | "NCHAR" | <K_CHAR> | "BPCHAR" | "TEXT" | "STRING" | <K_CHARACTER> | "VARYING"> | ||
| | <#TYPE_VARCHAR2: <K_VARCHAR2>> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should got to TYPE_VARCHAR since we try to establish a reasonable grouping please.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that was left over from me figuring it out
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a problem. When I move this into the TYPE_VARCHAR, the generated TokenManager gets a code too large. I guess we're reaching the limits of JavaCC again...
I'll have to look into why exactly this happens, but I've not applied this change yet in my last commit.
src/main/java/net/sf/jsqlparser/util/validation/validator/ExpressionValidator.java
Outdated
Show resolved
Hide resolved
src/main/java/net/sf/jsqlparser/util/deparser/SelectDeParser.java
Outdated
Show resolved
Hide resolved
src/main/java/net/sf/jsqlparser/util/deparser/ExpressionDeParser.java
Outdated
Show resolved
Hide resolved
src/main/java/net/sf/jsqlparser/statement/select/FromItemVisitorAdapter.java
Show resolved
Hide resolved
src/main/java/net/sf/jsqlparser/expression/JsonQueryWrapperType.java
Outdated
Show resolved
Hide resolved
src/main/java/net/sf/jsqlparser/expression/ExpressionVisitorAdapter.java
Outdated
Show resolved
Hide resolved
Keep the nit-picking coming :) There's still some features missing before I'll consider this PR ready for merge. |
@ANeumann82 Great Work!! Can you please let me know the ETA for this change |
|
@ANeumann82: How can we move this forward together? What assistance can I provide please? |
# Conflicts: # src/main/java/net/sf/jsqlparser/util/deparser/ExpressionDeParser.java # src/main/jjtree/net/sf/jsqlparser/parser/JSqlParserCC.jjt
|
@manticore-projects Sorry for the long silence. I've been into a rabbit hole of JavaCC and other parsers... I've updated the PR from the master branch, but now I get "code too large" in the generated "CCJsqlParserTokenManager.java". Do you have any idea to work around that problem? I don't know if there's anything we can do about that with the current JavaCC version. I'm currently looking into alternative parsers to maybe replace JavaCC in JSQLParser at some point, but that's not easy. |
Have done that, have been there and you are welcome.
I will lodge a case with the JavaCC team, maybe they can help.
We have too many token apparently. I want to check first if the JavaCC team can help.
I am most interested in this one too and dug deep already. Unfortunately there is not really any good alternative, but maybe |
No description provided.