Export (0) Print
Expand All
0 out of 2 rated this helpful - Rate this topic

Procedure Call Escape Sequence

ODBC uses escape sequences for procedure calls. The syntax of this escape sequence is as follows:

{[?=]call procedure-name[([parameter][,[parameter]]...)]}

In BNF notation, the syntax is as follows:

ODBC-procedure-escape ::=

     | ODBC-esc-initiator [?=] call procedure ODBC-esc-terminator

procedure ::= procedure-name | procedure-name (procedure-parameter-list)

procedure-identifier ::= user-defined-name

procedure-name ::= procedure-identifier

     | owner-name.procedure-identifier

     | catalog-name catalog-separator procedure-identifier

     | catalog-name catalog-separator [owner-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}

(The catalog separator is returned through SQLGetInfo with the SQL_CATALOG_NAME_SEPARATOR information option.)

procedure-parameter-list ::= procedure-parameter

     | procedure-parameter, 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 whether 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.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.