From: Bob Ippolito <bob@redivi.com>
To: nathan wagner <nw@hydaspes.if.org>
Cc: pgsql-hackers@postgresql.org
Subject: Re: uuid type for postgres
Date: Tue, 6 Sep 2005 14:11:45 -0700
Message-ID: <5033E692-1E9E-425B-A807-64BF7F4EB3F1@redivi.com> (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 Sep 6, 2005, at 2:16 PM, 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.
>
>
>> 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.
>
>
>> Couldn't you just fix the
>> problem in pguuid rather than 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.
It's not that hard to get a MAC address or serial number out of a
Mac, the problem is I'm not going to bother writing that code for a
GPL extension to PostgreSQL. There's a better way, anyhow. Darwin
ships with UUID parse/generate/etc functions in its Libc (<uuid/
uuid.h>).
FWIW, that code (the Theodore Ts'o UUID implementation) looks to be
suitably licensed for PostgreSQL, and it actually it appears that
someone has already written a PostgreSQL UUID type using this it...
which is unfortunately LGPL'ed (why?!).
-bob
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: bob@redivi.com, nw@hydaspes.if.org, pgsql-hackers@postgresql.org
Subject: Re: uuid type for postgres
In-Reply-To: <5033E692-1E9E-425B-A807-64BF7F4EB3F1@redivi.com>
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> <5033E692-1E9E-425B-A807-64BF7F4EB3F1@redivi.com>
* 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