Skip to content
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

More detailed parse error reporting #75

Closed
TaoK opened this issue Sep 9, 2012 · 2 comments
Closed

More detailed parse error reporting #75

TaoK opened this issue Sep 9, 2012 · 2 comments

Comments

@TaoK
Copy link
Owner

TaoK commented Sep 9, 2012

Jeff Clark suggests that it would be nice if the formatter pin-pointed the apparent location in the SQL, of the error. In an HTML output it could be highlighted, for example, and in text output it could be marked with a comment.

@TaoK
Copy link
Owner Author

TaoK commented Sep 9, 2012

No comment for now, seems like it would do more harm than good - might consider adding it as an option at a later time

@TaoK
Copy link
Owner Author

TaoK commented Sep 9, 2012

Closing this for now, might consider adding a SQL Comment in the likely spot (end of the detected error region) for NON-colorizing SQL if there is any demand.

@TaoK TaoK closed this as completed Sep 9, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant