Procedure Call Escape Sequence
{[?=]call procedure-name[([parameter][,[parameter]]...)]}
In BNF notation, the syntax is as follows:
ODBC-procedure-escape ::=
procedure ::= procedure-name | procedure-name (procedure-parameter-list)
procedure-identifier ::= user-defined-name
procedure-name ::= procedure-identifier
(The third syntax is valid only if the data source does not support owners.)
owner-name ::= user-defined-name
catalog-name ::= user-defined-name
catalog-separator ::= {implementation-defined}
procedure-parameter-list
procedure-parameter ::= dynamic-parameter | literal | empty-string
empty-string ::= {
ODBC-esc-initiator ::= {
ODBC-esc-terminator ::= }
(If a procedure parameter is an empty string, the procedure uses the default
value for that parameter.)
To determine if the data source supports procedures and the driver supports
the ODBC procedure invocation syntax, an application can call SQLGetInfo with the SQL_PROCEDURES information type.
| ODBC-esc-initiator [?=] call procedure ODBC-esc-terminator
| owner-name.procedure-identifier
| catalog-name catalog-separator procedure-identifier
| catalog-name catalog-separator [owner-name].procedure-identifier
(The catalog separator is returned through SQLGetInfo with the SQL_CATALOG_NAME_SEPARATOR information option.)
| procedure-parameter, procedure-parameter-list