From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Mark Mielke <mark(at)mark(dot)mielke(dot)cc> |
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 15:01:57 |
Message-ID: | 28121.1223650917@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2008-10-10 15:46:29 | Re: 8.4devel out of memory |
Previous Message | Robert Haas | 2008-10-10 15:01:22 | Re: patch: Allow the UUID type to accept non-standard formats |