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.

Sign up for GitHub

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

Jump to bottom

Better error messages when inside of SQL #26

Open

dedmen opened this issue Apr 9, 2020 · 0 comments

Member

dedmen commented Apr 9, 2020

22:15:51 Error in expression <interceptOnFrame>
22:15:51   Error position: <interceptOnFrame>
22:15:51   Error Intercept-DB exception: Can't connect twice. Already connected
at
CALL StoredProcedureName(?, ?);

Bad. don't want that interceptOnFrame :/ Is there a way around that?

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment