-
Notifications
You must be signed in to change notification settings - Fork 19
SQL parser #23
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
Comments
I think it's doing just enough parsing to syntax highlight… link. |
Lexer and parser generated with antlr4 for go seems to be working okay. |
@sri-soham: seems interesting. would you be up for a PR ? :) |
@sbinet : Files generated make use of the antlr go libraries. Java and the antlr jar file will not be needed though. About the PR: I am new to lexer/parser business. It will take time. |
From what I have understood, sqlite3 generates bytecode by traversing through the parse tree. That bytecode and engine are internal to sqlite3 and can change without notice. https://www.sqlite.org/opcode.html What do I do after parse tree is built? Generate golang struct for each type of statement or something else? |
We'd need a SQLite 3 SQL statements parser.
Possible candidate(s?) before writing our own:
The text was updated successfully, but these errors were encountered: