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

New "escapeSyntaxCallMode" connection property #1560

Merged
merged 1 commit into from Nov 26, 2019

Commits on Nov 26, 2019

  1. feat: add new "escapeSyntaxCallMode" connection property

    The "escapeSyntaxCallMode" connection property allows you to specify how the driver transforms
    JDBC escape call syntax into underlying SQL, for invoking procedures and functions.
    The possible values of this property are: select, callIfNoReturn, or call
    In escapeSyntaxCallMode=select mode (the default), the driver always uses a SELECT statement
    (allowing function invocation only).
    In escapeSyntaxCallMode=callIfNoReturn mode, the driver uses a CALL statement (allowing
    procedure invocation) if there is no return parameter specified, otherwise the driver uses a
    SELECT statement.
    In escapeSyntaxCallMode=call mode, the driver always uses a CALL statement (allowing procedure
    invocation only).
    Prior to the addition of this connection property, the driver always used a SELECT statement for
    JDBC escape call syntax, which results in the following error when attempting to invoke a
    procedure:
        ERROR: xxxx is a procedure  Hint: To call a procedure, use CALL
    gregn123 committed Nov 26, 2019
    Copy the full SHA
    e1f7aea View commit details
    Browse the repository at this point in the history