| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | mohd(dot)akram(at)live(dot)com |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14670: uuid_generate_v3 and uuid_generate_v5 do not support binary names |
| Date: | 2017-05-24 21:26:54 |
| Message-ID: | CAKFQuwbEd_2nTuf6oXojAR39ycz8CASy6TfvCBfm_gRtGP6EOw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, May 24, 2017 at 1:46 PM, <mohd(dot)akram(at)live(dot)com> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 14670
> Logged by: Mohamed Akram
> Email address: mohd(dot)akram(at)live(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mohamed Akram | 2017-05-24 21:54:00 | Re: BUG #14670: uuid_generate_v3 and uuid_generate_v5 do not support binary names |
| Previous Message | mohd.akram | 2017-05-24 20:46:37 | BUG #14670: uuid_generate_v3 and uuid_generate_v5 do not support binary names |