From: David Fetter <david@fetter.org>
To: nathan wagner <nw@hydaspes.if.org>
Cc: pgsql-hackers@postgresql.org
Subject: Re: uuid type for postgres
Date: Tue, 6 Sep 2005 13:49:28 -0700
Message-ID: <20050906204928.GC24864@fetter.org> (raw)
In-Reply-To: <20050906211613.GB26851@granicus.if.org>
References: <20050906135057.GA24136@granicus.if.org>
<20050906144930.GA27641@mark.mielke.cc>
<200509061002.43803.josh@agliodbs.com>
<36e6829205090612575b954f38@mail.gmail.com>
<20050906211613.GB26851@granicus.if.org>
On Tue, Sep 06, 2005 at 09:16:13PM +0000, nathan wagner wrote:
> On Tue, Sep 06, 2005 at 03:57:55PM -0400, jonah.harris@gmail.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@fetter.org http://fetter.org/
phone: +1 510 893 6100 mobile: +1 415 235 3778
Remember to vote!
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: david@fetter.org, nw@hydaspes.if.org, pgsql-hackers@postgresql.org
Subject: Re: uuid type for postgres
In-Reply-To: <20050906204928.GC24864@fetter.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox