mirror of
https://github.com/FirebirdSQL/firebird.git
synced 2025-01-24 01:23:03 +01:00
Fix - thanks Paul Vinkenoog.
This commit is contained in:
parent
ea15a3fae3
commit
ac27ffa89a
@ -247,7 +247,7 @@ Format:
|
|||||||
CHAR_TO_UUID( <string> )
|
CHAR_TO_UUID( <string> )
|
||||||
|
|
||||||
Notes:
|
Notes:
|
||||||
If you have not used this function before, its usage is discouraged. CHAR_TO_UUID2 superseds it.
|
If you have not used this function before, its usage is discouraged. CHAR_TO_UUID2 supersedes it.
|
||||||
|
|
||||||
Example:
|
Example:
|
||||||
select char_to_uuid('93519227-8D50-4E47-81AA-8F6678C096A1') from rdb$database;
|
select char_to_uuid('93519227-8D50-4E47-81AA-8F6678C096A1') from rdb$database;
|
||||||
@ -268,7 +268,7 @@ Format:
|
|||||||
CHAR_TO_UUID2( <string> )
|
CHAR_TO_UUID2( <string> )
|
||||||
|
|
||||||
Notes:
|
Notes:
|
||||||
This function superseds CHAR_TO_UUID. The difference between them is that CHAR_TO_UUID does a
|
This function supersedes CHAR_TO_UUID. The difference between them is that CHAR_TO_UUID does a
|
||||||
byte-by-byte conversion of the ASCII string to the OCTETS one, while CHAR_TO_UUID2 converts
|
byte-by-byte conversion of the ASCII string to the OCTETS one, while CHAR_TO_UUID2 converts
|
||||||
a RFC-4122 compliant ASCII UUID to a compliant OCTETS string.
|
a RFC-4122 compliant ASCII UUID to a compliant OCTETS string.
|
||||||
|
|
||||||
@ -870,7 +870,7 @@ Format:
|
|||||||
UUID_TO_CHAR( <string> )
|
UUID_TO_CHAR( <string> )
|
||||||
|
|
||||||
Notes:
|
Notes:
|
||||||
If you have not used this function before, its usage is discouraged. UUID_TO_CHAR2 superseds it.
|
If you have not used this function before, its usage is discouraged. UUID_TO_CHAR2 supersedes it.
|
||||||
|
|
||||||
Example:
|
Example:
|
||||||
select uuid_to_char(gen_uuid()) from rdb$database;
|
select uuid_to_char(gen_uuid()) from rdb$database;
|
||||||
@ -890,7 +890,7 @@ Format:
|
|||||||
UUID_TO_CHAR2( <string> )
|
UUID_TO_CHAR2( <string> )
|
||||||
|
|
||||||
Notes:
|
Notes:
|
||||||
This function superseds UUID_TO_CHAR. The difference between them is that UUID_TO_CHAR does a
|
This function supersedes UUID_TO_CHAR. The difference between them is that UUID_TO_CHAR does a
|
||||||
byte-by-byte conversion of the OCTETS string to the ASCII one, while UUID_TO_CHAR2 converts
|
byte-by-byte conversion of the OCTETS string to the ASCII one, while UUID_TO_CHAR2 converts
|
||||||
a RFC-4122 compliant OCTETS UUID to a compliant ASCII string.
|
a RFC-4122 compliant OCTETS UUID to a compliant ASCII string.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user