| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x |
| Date: | 2008-02-29 03:56:53 |
| Message-ID: | 21410.1204257413@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Sullivan <ajs(at)crankycanuck(dot)ca> writes:
> "Be conservative in what you send, and liberal in what you accept."
Yeah, I was about to quote that same maxim myself. I don't have a big
problem with allowing uuid_in to accept known format variants. (I'm
not sure about allowing a hyphen *anywhere*, because that could lead to
accepting things that weren't meant to be a UUID at all, but this HP
format seems regular enough that that's not a serious objection to it.)
What I was really complaining about was Josh's suggestion that we invent
a function to let users *output* UUIDs in random-format-of-the-week.
I can't imagine much good coming of that. I think we should keep
uuid_out emitting only the RFC-standardized format.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-02-29 04:03:31 | Re: OSSP can be used in the windows environment now! |
| Previous Message | Tom Lane | 2008-02-29 03:45:24 | Re: CREATE TABLE, load and freezing |