jdbc: escape syntax: stored procedures and functions

[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

[Totktonada]

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.

[Totktonada]

See also #79.

[Totktonada]

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.