From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | nathan wagner <nw(at)hydaspes(dot)if(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: uuid type for postgres |
Date: | 2005-09-06 20:49:28 |
Message-ID: | 20050906204928.GC24864@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
On Tue, Sep 06, 2005 at 09:16:13PM +0000, nathan wagner wrote:
> On Tue, Sep 06, 2005 at 03:57:55PM -0400, jonah(dot)harris(at)gmail(dot)com wrote:
> > I agree with Josh on the UUID type, it gets abused far too often
>
> Out of curiosity, how does it get abused? It doesn't seem to me
> that it would be any more prone to abuse than any other type.
A typical abuse, as I have seen it, is for OO coders on the front-end
to turn the entire databse into what amounts to an associative array.
It then becomes somewhere between difficult and impossible to get good
performance, as UUID is the only thing useful as a PK/FK.
> > and (IMHO) isn't widely enough used to belong in the core.
>
> Seems like a self-fulfilling cycle. There isn't one in core or
> contrib (pguuid is not in contrib, IIRC), and so one doesn't get
> used. Since no one uses one, it's not in core or contrib.
In this case, not having it easy to get to is, IMHO, an *excellent*
idea. The whole thing is a giant foot-gun.
Just my $.02.
Cheers,
D
--
David Fetter david(at)fetter(dot)org http://fetter.org/
phone: +1 510 893 6100 mobile: +1 415 235 3778
Remember to vote!
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-09-06 20:53:07 | Re: PITR on different hardware |
Previous Message | mark | 2005-09-06 20:38:11 | Re: uuid type for postgres |
From | Date | Subject | |
---|---|---|---|
Next Message | Bob Ippolito | 2005-09-06 21:11:45 | Re: uuid type for postgres |
Previous Message | mark | 2005-09-06 20:38:11 | Re: uuid type for postgres |