You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error Description
After successfully configuring the LLM and database, when attempting to use CrackSQL's translate.py to convert PostgreSQL statements, the program encountered an error during parsing of the PostgreSQL statement as shown below:
Root Cause:
In the file ./CrackSQL/backend/preprocessor/antlr_parser/pg_parser/PostgreSQLParser.py, line 35398 the ParseRoutineBody function was undefined. The call of this function will certainly bring about error.
Temporary Solution:
After commenting out this line, the program ran successfully without obvious bug.
I think the tiny change of the code will make the repo better. However, I'm not sure that whether this solution is robust and elegant. Thanks, and looking forward to your insights!
The text was updated successfully, but these errors were encountered:
@Niax23 Thanks for your reports.
This issue is duplicated at #7. It is relevant to the generated ANTLR parser, not CrackSQL. There also exist one PR to resolve this issue at #19. You can consider to replace the files in the PR to see if such issue persists.
Uh oh!
There was an error while loading. Please reload this page.
After successfully configuring the LLM and database, when attempting to use CrackSQL's
translate.py
to convert PostgreSQL statements, the program encountered an error during parsing of the PostgreSQL statement as shown below:In the file
./CrackSQL/backend/preprocessor/antlr_parser/pg_parser/PostgreSQLParser.py
, line 35398 theParseRoutineBody
function was undefined. The call of this function will certainly bring about error.After commenting out this line, the program ran successfully without obvious bug.
I think the tiny change of the code will make the repo better. However, I'm not sure that whether this solution is robust and elegant. Thanks, and looking forward to your insights!
The text was updated successfully, but these errors were encountered: