X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4D13FD88C1 for ; Tue, 6 Sep 2005 16:58:05 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 68846-01 for ; Tue, 6 Sep 2005 19:57:57 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.199]) by svr1.postgresql.org (Postfix) with ESMTP id D336BD8781 for ; Tue, 6 Sep 2005 16:57:53 -0300 (ADT) Received: by rproxy.gmail.com with SMTP id 34so241733rns for ; Tue, 06 Sep 2005 12:57:55 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=TFz8E536qU6fB7a42HlcPkgg+N4r/lvKec/H1UHBgXh82s3dn0RwttnaoLUbngd7BsP3nY3b2j8DUJ4nGu8jRmgJ4/uDgDYaO6MzwD7xyspOLpyDaTJiTH+VOMp4GUdDyK1bcSCW38G/f2YbX6CitokiWLf7S5BKEbNi1h/t7l4= Received: by 10.11.119.26 with SMTP id r26mr95956cwc; Tue, 06 Sep 2005 12:57:55 -0700 (PDT) Received: by 10.11.119.38 with HTTP; Tue, 6 Sep 2005 12:57:55 -0700 (PDT) Message-ID: <36e6829205090612575b954f38@mail.gmail.com> Date: Tue, 6 Sep 2005 15:57:55 -0400 From: "Jonah H. Harris" Reply-To: jonah.harris@gmail.com To: josh@agliodbs.com Subject: Re: uuid type for postgres Cc: pgsql-hackers@postgresql.org, mark@mark.mielke.cc, nathan wagner In-Reply-To: <200509061002.43803.josh@agliodbs.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_3430_20391779.1126036675642" References: <20050906135057.GA24136@granicus.if.org> <20050906144930.GA27641@mark.mielke.cc> <200509061002.43803.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.305 required=5 tests=[AWL=-0.224, HTML_20_30=0.504, HTML_MESSAGE=0.001, RCVD_BY_IP=0.024] X-Spam-Level: X-Archive-Number: 200509/269 X-Sequence-Number: 72666 ------=_Part_3430_20391779.1126036675642 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I agree with Josh on the UUID type, it gets abused far too often and (IMHO)= =20 isn't widely enough used to belong in the core. Couldn't you just fix the= =20 problem in pguuid rather than write a whole new type? On 9/6/05, Josh Berkus wrote: >=20 > Mark, >=20 > > I suggest that UUID be recommended in place of SERIAL for certain > > classes of applications, and that it therefore belongs in the core. > > UUID and SERIAL can be used together (although, once you have a UUID, > > it may not be useful to also have a SERIAL). >=20 > I think that, if you want to push a refactored UUID type for PostgreSQL > 8.2, that you'd better separate your database design arguments from your > inclusion arguments. >=20 > For example, you might get my agreement that it would be useful to have a > UUID as a core type; you would *never* get my agreement to recommend usin= g > UUID to newbies. I have seen *far* too many abuses of UUIDs in really > bad database design. People who use them should be experienced enough to > know what they're doing. >=20 > -- > --Josh >=20 > Josh Berkus > Aglio Database Solutions > San Francisco >=20 > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match > ------=_Part_3430_20391779.1126036675642 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I agree with Josh on the UUID type, it gets abused far too often and (IMHO) isn't widely enough used to belong in the core.  Couldn't you j= ust fix the problem in pguuid rather than write a whole new type?

On 9/6/05, Josh Berkus <josh@agliodbs.com> wrote: Mark,

> I suggest that UUID be recommended in place of SERIAL for= certain
> classes of applications, and that it therefore belongs in = the core.
> UUID and SERIAL can be used together (although, once you = have a UUID,
> it may not be useful to also have a SERIAL).

I think that, = if you want to push a refactored UUID type for PostgreSQL
8.2, that you'= d better separate your database design arguments from your
inclusion arg= uments.

For example, you might get my agreement that it would be useful to = have a
UUID as a core type; you would *never* get my agreement to recomm= end using
UUID to newbies.   I have seen *far* too many abuses= of UUIDs in really
bad database design.   People who use them should be experien= ced enough to
know what they're doing.

--
--Josh

Josh B= erkus
Aglio Database Solutions
San Francisco

-----------------= ----------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to       choose an index scan if your joining = column's datatypes do not
       match
=

------=_Part_3430_20391779.1126036675642--