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 75993D8720 for ; Tue, 6 Sep 2005 17:32:10 -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 76097-09 for ; Tue, 6 Sep 2005 20:32:06 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.203]) by svr1.postgresql.org (Postfix) with ESMTP id F4161D86B2 for ; Tue, 6 Sep 2005 17:32:04 -0300 (ADT) Received: by rproxy.gmail.com with SMTP id 40so241948rnz for ; Tue, 06 Sep 2005 13:32:06 -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=qC/iOvLnevUU/31q3dcXbfeCci3EQcEMdpfpAdcrx/I3xrW0OE0bPOX5lE5aSEWS4TmHmvhXfGQHKSVuQDCRfVwEAHjGPRiaKsku+1VWBxoTuO4v9KnjVPJpOb8+r17BDxeruRRsBEvPgzFI9xg7ZcQ9+INJMmZpTvRkEvJFPcY= Received: by 10.11.119.40 with SMTP id r40mr16240cwc; Tue, 06 Sep 2005 13:32:06 -0700 (PDT) Received: by 10.11.119.38 with HTTP; Tue, 6 Sep 2005 13:32:06 -0700 (PDT) Message-ID: <36e6829205090613322d300745@mail.gmail.com> Date: Tue, 6 Sep 2005 16:32:06 -0400 From: "Jonah H. Harris" Reply-To: jonah.harris@gmail.com To: nathan wagner Subject: Re: uuid type for postgres Cc: pgsql-hackers@postgresql.org In-Reply-To: <20050906211613.GB26851@granicus.if.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_3486_1308177.1126038726065" 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> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.417 required=5 tests=[AWL=-0.112, HTML_20_30=0.504, HTML_MESSAGE=0.001, RCVD_BY_IP=0.024] X-Spam-Level: X-Archive-Number: 200509/273 X-Sequence-Number: 72670 ------=_Part_3486_1308177.1126038726065 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline The only time I've seen someone use UUIDs in PostgreSQL is when they were= =20 converting from SQL Server. I've seen many bad data models using UUID that= =20 could've/should've used normal sequences for portability. I look forward to seeing you're code. Thanks! On 9/6/05, nathan wagner wrote: >=20 > 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 >=20 > 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. >=20 > > and (IMHO) isn't widely enough used to belong in the core. >=20 > 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. >=20 > > Couldn't you just fix the > > problem in pguuid rather than write a whole new type? >=20 > Not sure which you you're addressing here, but I can't fix the license > problem. Nor can I readily fix the lack of a mac ioctl() to get > the hardware mac address. >=20 > In any case, from an economy of effort view, I'd much rather maintain > a postgres extension/interface to an existing uuid library, than fret > the details of writing a uuid library myself. UUIDs themselves don't > really interest me, I just happen to need one for my application. >=20 > I'm basically done. I'll tar it up and post a link to an alpha version in= =20 > a > couple of hours. As far as i can tell, it works fine. I'm calling it alph= a > because i'm not doing proper error checking, and i'm not sure how to log= =20 > or > throw an error even if i detect one. Also, I have only compiled it on > Mac OS 10.3, I'll want to test it on my linux box. >=20 > -- > Nathan Wagner >=20 > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend > ------=_Part_3486_1308177.1126038726065 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline The only time I've seen someone use UUIDs in PostgreSQL is when they were converting from SQL Server.  I've seen many bad data models using UUID that could've/should've used normal sequences for portability.

I look forward to seeing you're code.

Thanks!


On 9/6/05, nathan wagner <nw@hydas= pes.if.org> 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.

&g= t; 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 cont= rib (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= .

> Couldn't you just fix the
> problem in pguuid rather th= an write a whole new type?

Not sure which you you're addressing here= , but I can't fix the license
problem.  Nor can I readily fix the lack of a mac ioctl() to = get
the hardware mac address.

In any case, from an economy of eff= ort view, I'd much rather maintain
a postgres extension/interface to an = existing uuid library, than fret
the details of writing a uuid library myself.  UUIDs themselv= es don't
really interest me, I just happen to need one for my applicatio= n.

I'm basically done.  I'll tar it up and post a link to = an alpha version in a
couple of hours.  As far as i can tell, it works fine. &= nbsp;I'm calling it alpha
because i'm not doing proper error checking, a= nd i'm not sure how to log or
throw an error even if i detect one. =  Also, I have only compiled it on
Mac OS 10.3, I'll want to test it on my linux box.

--
Nathan = Wagner

---------------------------(end of broadcast)----------------= -----------
TIP 6: explain analyze is your friend

------=_Part_3486_1308177.1126038726065--