| title | GUID Escape Sequences | |||
|---|---|---|---|---|
| description | GUID Escape Sequences | |||
| author | dlevy-msft-sql | |||
| ms.author | dlevy | |||
| ms.reviewer | davidengel, sunilbs, mcimfl | |||
| ms.date | 01/19/2017 | |||
| ms.service | sql | |||
| ms.subservice | connectivity | |||
| ms.topic | reference | |||
| helpviewer_keywords |
|
ODBC uses escape sequences for GUID literals. The syntax of this escape sequence is as follows:
{guid 'nnnnnnnn-nnnn-nnnn-nnnn-nnnnnnnnnnnn'}
In BNF notation, the syntax is as follows:
ODBC-guid-escape ::=
ODBC-esc-initiator guid 'guid-value' ODBC-esc-terminator
ODBC-esc-initiator ::= {
ODBC-esc-terminator ::= }
guid-value ::= clock-low-value guid-separator clock-middle-value guid-separator clock-high-value guid-separator clock-seq-value guid-separator node-value
guid-separator ::= -
clock-low-value ::= hex_digit hex_digit hex_digit hex_digit hex_digit hex_digit hex_digit hex_digit
clock-middle-value ::= hex_digit hex_digit hex_digit hex_digit
clock-high-value ::= hex_digit hex_digit hex_digit hex_digit
clock-seq-value ::= hex_digit hex_digit hex_digit hex_digit
clock-node-value ::= hex_digit hex_digit hex_digit hex_digit hex_digit hex_digit hex_digit hex_digit hex_digit hex_digit hex_digit hex_digit
hex_digit ::= 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | A | B | C | D | E | F
The GUID literal escape sequence is supported if the GUID data type is supported by the data source. An application should call SQLGetTypeInfo to determine whether this data type is supported.