Firebird 6 introduces the CALL statement as an alternative to call executable stored procedures and excluding/limiting "out" parameters, and support for explicitly identifying the procedure or function parameter by name (also in EXECUTE PROCEDURE and selects). The SQL parser probably needs to be enhanced to support this (parts of this may need to be backported to Jaybird 6 and maybe 5), and additionally we need to add support for using CALL (not to be confused with the JDBC CALL-escape) and named parameters for CallableStatement.
Exact level of support needs to be evaluated and determined (e.g. should we also support the setXXX methods with a name instead of index?).
See also:
This issue may need to be split up further.
Firebird 6 introduces the
CALLstatement as an alternative to call executable stored procedures and excluding/limiting "out" parameters, and support for explicitly identifying the procedure or function parameter by name (also inEXECUTE PROCEDUREand selects). The SQL parser probably needs to be enhanced to support this (parts of this may need to be backported to Jaybird 6 and maybe 5), and additionally we need to add support for using CALL (not to be confused with the JDBC CALL-escape) and named parameters forCallableStatement.Exact level of support needs to be evaluated and determined (e.g. should we also support the setXXX methods with a name instead of index?).
See also:
This issue may need to be split up further.