Code too large #2161
Replies: 7 comments 4 replies
-
Greetings. I was worried that we will hit this at a time. Its a limitation of JavaCC when the Grammar is too complex and the generated Parser becomes to large (beyond the 64kb mark). In general, its a JavaCC issue and should be discussed there.
|
Beta Was this translation helpful? Give feedback.
-
I opened a case at JavaCC, see javacc/javacc#297 |
Beta Was this translation helpful? Give feedback.
-
Hi @manticore-projects , The error occurs in the So I guess my implementation is being blocked by that problem and we need to wait for a solution or workaround provided at JavaCC. |
Beta Was this translation helpful? Give feedback.
-
@ssteinhauser: please give it a few days to collect feedback and then we will look for an acceptable way forward. |
Beta Was this translation helpful? Give feedback.
-
Hi.
You'll have to change yous Tell me how things evolve. |
Beta Was this translation helpful? Give feedback.
-
Hi
By the way: the version you�ll find on Maven Central is 8.0.1; I�m on a
8.1.0 version, currently not released; it has a lot of �laundry� changes but
with normally no impact; main benefits for users should be prettier
generated code and better debug traces (lookahead, token manager, parser).
Will it be possible for you to check without too much effort that JSqlParser
works fine with 8.0.1, and then spend more time checking it works with 8.1.0
(for example on performance, traces�)?
TIA
Regards
Marc
De : manticore-projects ***@***.***>
Envoyé : mardi 11 février 2025 12:16
À : JSQLParser/JSqlParser ***@***.***>
Cc : Marc MAZAS ***@***.***>; Mention ***@***.***>
Objet : Re: [JSQLParser/JSqlParser] Code too large (Discussion #2161)
@MarcMazas <https://github.com/MarcMazas> : Thank you a lot! I definitely
will give this a try soonest and appreciate your help and support. I will
return with findings and hopefully a success story.
Cheers and best
Andreas
�
Reply to this email directly, view it on GitHub
<#2161 (comment)
-12139319> , or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFQZRCZ7KCWMSSRUQHJOKUL2P
HLVHAVCNFSM6AAAAABW2GOQPOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTE
MJTHEZTCOI> .
You are receiving this because you were mentioned.
<https://github.com/notifications/beacon/AFQZRCYXTCVE7Z6DJ6MD5GL2PHLVHA5CNFS
M6AAAAABW2GOQPOWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3T
UL5UWJTQAXE5TO.gif> Message ID:
***@***.***
***@***.***
.com> >
|
Beta Was this translation helpful? Give feedback.
-
About the "Code too large" issue: from what I've seen, you had 2 errrors:
|
Beta Was this translation helpful? Give feedback.
-
Hi,
I am currently struggling with the Code too large problem while I am trying to implement the
IMPORT
andEXPORT
statements of Exasol (https://docs.exasol.com/db/latest/sql/import.htm / https://docs.exasol.com/db/latest/sql/export.htm).You can see the current progress of my implementation here: https://github.com/ssteinhauser/JSqlParser/tree/feature/exasol-import-export
Did anyone already experience this problem and can provide a solution for that?
Thank you in advance!
Beta Was this translation helpful? Give feedback.
All reactions