Re: [BUGS] BUG #14670: uuid_generate_v3 and uuid_generate_v5 do notsupport binary names
| От | Mohamed Akram |
|---|---|
| Тема | Re: [BUGS] BUG #14670: uuid_generate_v3 and uuid_generate_v5 do notsupport binary names |
| Дата | |
| Msg-id | 48023522-741C-4239-A908-3153C00DF35D@outlook.com обсуждение исходный текст |
| Ответ на | Re: [BUGS] BUG #14670: uuid_generate_v3 and uuid_generate_v5 do notsupport binary names ("David G. Johnston" <david.g.johnston@gmail.com>) |
| Ответы |
Re: [BUGS] BUG #14670: uuid_generate_v3 and uuid_generate_v5 do not support binary names
|
| Список | pgsql-bugs |
That’s true, I guess it’s more of an enhancement but I couldn’t find an option for that in the bug form. However, even the sample C code in the RFC takes a void* argument for name.
My use case is generating unique identifiers for images, similar to:
where data is a bytea column.
I know I can convert to base64, but I’d rather not.
On May 25, 2017, at 1:26 AM, David G. Johnston <david.g.johnston@gmail.com> wrote:The following bug has been logged on the website:
Bug reference: 14670
Logged by: Mohamed Akram
Email address: mohd.akram@live.com
PostgreSQL version: 9.6.3
Operating system: macOS 10.12.5
Description:
As per RFC 4122 - https://tools.ietf.org/html/rfc4122#section-4.3 - name
should not be limited to textual data.Since it says should and not must an implementation that restricts the name to be textual is still conforming.Apart from that supplying an SQL example of what you want to work and what happens when it fails would reduce the possibility of mis-understanding what it is you are saying.David J.
В списке pgsql-bugs по дате отправления: