-
Notifications
You must be signed in to change notification settings - Fork 63
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
Support EXECUTE IMMEDIATE #128
Conversation
f9dd164
to
e39b174
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the driver will error with older servers unless explicitPrepare
is explicitly set, do we have some sort of release notes?
Nope, you need to enable For tracking breaking changes in release notes, I'm adding more configuration in #127 |
I see now but the comment is confusing - |
Should be |
I might have messed it up because I initially assumed the JDBC driver would have this turned on by default, only to later notice it's the opposite, so I also changed it here accordingly. Will double-check, thanks for noticing! |
the implementation seems correct, just the PR description seems wrong/ |
Use EXECUTE IMMEDIATE sent in the HTTP request body, instead of putting the query text in HTTP headers. This should allow sending large query text. It can be enabled by setting the `explicitPrepare` option to false in the connection string.
e39b174
to
802a610
Compare
Use EXECUTE IMMEDIATE sent in the HTTP request body, instead of putting the query text in HTTP headers. This should allow sending large query text. It can be enabled by setting the
explicitPrepare
option to false in the connection string.Fixes #123 and fixes #118