Escape clause syntax

Because ODBC vendor escape clauses are implemented identically across all products and vendors, ODBC defines a short-form escape clause that includes only the extended SQL text.

Db2 ODBC supports the following short-form escape clause:

{ extended SQL text }

extended SQL text: In ODBC, the string of extended SQL that the ODBC driver translates to data source specific SQL.

This short-form escape clause that does not conform to X/Open specifications, but it is widely used among ODBC drivers. In ODBC 3.0, the short ODBC format replaces the deprecated long X/Open format.

Db2 ODBC supports the SQL escape clause X/Open defines with the following long-form syntax:

--(*vendor(vendor-identifier),
      product(product-identifier) extended SQL text*)--

vendor-identifier: Vendor identification that is consistent across all of that vendor's SQL products. (For Db2 ODBC, this identifier can be set to either IBM® or Microsoft.)
product-identifier: Identifier for an SQL product. (For Db2 ODBC, this identifier is always set to ODBC.)
extended SQL text: The same text that the short-form escape clause uses.

Long-form vendor escape clauses are considered deprecated in ODBC 3.0. Although Db2 ODBC supports both long and short formats, you should use the current, short-form escape clauses in your applications.