-
Notifications
You must be signed in to change notification settings - Fork 81
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
Line and column numbers for syntax errors #24
Comments
Would be really nice to get this working. Then the results can be used as LSP |
@kyleconroy The
So it looks like a PgQueryError error has:
Which then is read by
So the
|
I believe #76 fixes this issue and this issue can now be closed, unless you are waiting until this is part of a release (as v4.2.0 from Feb 8 does not contain this change from Mar 10 ). By the way, thanks very much for this work! This is very much appreciated, as is the rest of your extremely useful library! |
@StevenACoffman Good catch - yes, I think this can be closed. I'm in the process of doing a 4.2.1 release, so this should also be officially released soon. |
When parsing a invalid query,
Parse
returns an error string starting with "syntax error ...". Would it be possible to get the offset of the syntax error, similar to SyntaxError type in the json package?Thanks again for the awesome package :) I'm using it to power my new project https://github.com/kyleconroy/sqlc
The text was updated successfully, but these errors were encountered: