Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in functions
| От | Aleksander Alekseev |
|---|---|
| Тема | Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in functions |
| Дата | |
| Msg-id | CAJ7c6TOpO7tL87fBpFEn6DQRfGzT8NQiNtDzE2XrhJQ0-FOmuA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in functions (Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>) |
| Ответы |
Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in functions
|
| Список | pgsql-hackers |
Hi,
Thanks for the patch.
> That does seem like a better fit. It's used mainly in recv functions,
> which this basically is (but user-callable).
>
> Updated patch attaced.
Perhaps bytea_uuid() should check the UUID format. Consider the
following example:
SELECT uuid_extract_version('\x019a2f859cedffffb99d9c55044a2563'::bytea::uuid);
uuid_extract_version
----------------------
15
There is no UUID version 15 according to RFC 9562, and the
documentation for uuid_extract_version() says:
"""
Extracts the version from a UUID of the variant described by RFC 9562.
For other variants, this function returns null. For example, for a
UUID generated by gen_random_uuid, this function will return 4.
"""
If I read this correctly, either bytea_uuid() should reject this, or
uuid_extract_version() should be modified to return NULL, or the
documentation for uuid_extract_version() should be altered.
--
Best regards,
Aleksander Alekseev
В списке pgsql-hackers по дате отправления: