We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am proposing to include the failing SQL in the exception message.
That will make it easier to find what code has failed by searching for the query in client codebase.
I already made a PR (#418), but Greeting action suggests posting an issue, so here it is :)
The text was updated successfully, but these errors were encountered:
Thank you for reporting an issue. See the wiki for documentation and gitter for questions.
Sorry, something went wrong.
No branches or pull requests
I am proposing to include the failing SQL in the exception message.
That will make it easier to find what code has failed by searching for the query in client codebase.
I already made a PR (#418), but Greeting action suggests posting an issue, so here it is :)
The text was updated successfully, but these errors were encountered: