From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Mark Mielke" <mark(at)mark(dot)mielke(dot)cc>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: patch: Allow the UUID type to accept non-standard formats |
Date: | 2008-10-10 19:35:40 |
Message-ID: | 162867790810101235s16f38d93h710c9bbf754e0017@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2008/10/10 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Mark Mielke <mark(at)mark(dot)mielke(dot)cc> writes:
>> Anyways - I only somewhat disagree. I remember the original discussions,
>> and I remember agreeing with the points to keep PostgreSQL UUID support
>> thin and rigid. It's valuable for it to be built-in to the database.
>> It's not necessarily valuable for PostgreSQL to support every UUID
>> version or every format. Supporting additional formats is the direction
>> of supporting every UUID format. Three months from now, somebody is
>> going to propose allowing '-' or ':'. What should the answer be then?
>
> Well, this discussion started with the conventional wisdom about "be
> conservative in what you send and liberal in what you accept". I'd
> still resist emitting any UUID format other than the RFC-approved one,
> but I don't see anything very wrong in being able to read common
> variants.
Is it problem do for non standard UUID formats pgfoundry project?
Regards
Pavel Stehule
>
> regards, tom lane
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2008-10-10 19:37:46 | Re: patch: Allow the UUID type to accept non-standard formats |
Previous Message | Kevin Grittner | 2008-10-10 18:58:47 | Re: How is random_page_cost=4 ok? |