Skip to content

jdbc: escape syntax: stored procedures and functions #82

Open

Description

@Totktonada

It is optional for user-defined and vendor-specific functions according to the JDBC standard. It is unclear whether it is required for scalar functions from Appendix C of the standard, so I leave it in the JDBC MVP milestone.

DatabaseMetadata.supportsStoredProcedures and DatabaseMetadata.supportsStoredFunctionsUsingCallSyntax should return true when it will be supported. It is not clear what is the difference btw these methods. AFAIU, the former one is about Appendix C functions, but the latter is about user-defined and vendor-defined functions.

The following DatabaseMetadata methods should return actual subsets of Appendix C functions:

  • getNumericFunctions
  • getStringFunctions
  • getSystemFunctions
  • getTimeDateFunctions

Activity

  1. added this to the JDBC MVP milestone on Nov 2, 2018
  2. Totktonada commented on May 20, 2019

    @Totktonada
    Author

    Tarantool now does not support stored procedures, but supports functions like max. At least we're able to call them like select max(...) and so it seems it worth to emulate call syntax on the driver side.

  3. Totktonada commented on May 20, 2019

    @Totktonada
    Author

    See also #79.

  4. Totktonada commented on Dec 3, 2019

    @Totktonada
    Author

    Store procedures / functions are callables that return one or several result set. So the issue is blocked on support of SQL/PSM or some alternative in tarantool itself. I'll move it to a later milestone.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockedNot ready to be implementedjdbc

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions