Re: Fixed length datatypes. WAS [GENERAL] UUID's as - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: Fixed length datatypes. WAS [GENERAL] UUID's as
Date
Msg-id 20060628173850.GJ44573@pervasive.com
Whole thread Raw
In response to Re: Fixed length datatypes. WAS [GENERAL] UUID's as  ("A.M." <agentm@themactionfaction.com>)
Responses Re: Fixed length datatypes. WAS [GENERAL] UUID's as  (mark@mark.mielke.cc)
Re: Fixed length datatypes. WAS [GENERAL] UUID's as  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Wed, Jun 28, 2006 at 01:18:39PM -0400, A.M. wrote:
> On Wed, June 28, 2006 1:14 pm, mark@mark.mielke.cc wrote:
> > On Wed, Jun 28, 2006 at 06:39:16PM +0200, Thomas Hallgren wrote:
> >
> >> Instead, I would like to humbly request the inclusion of a UUID
> >> datatype (or an opaque 128 bit datatype) in the core package. It's
> >> increasingly common and some databases (MS SQLServer) already have built
> >> in support for it.
> >
> > We have it. We're just not putting in the effort required to have it
> > included in core, as it's too much effort to convince people that the type
> > has value, that is is generic, and would be widely used without being
> > abused. All the geometric types that I'll never use in core, with few or
> > no uses, including functions to operate on these types, and no UUID
> > type... Hehe... To me, that's irony... :-)
> 
> Is it on pgfoundry? From past discussions, the new criteria for getting
> something into core is to first determine if it is successful on
> pgfoundry.

If http://lnk.nu/pgfoundry.org/a86.php is accurate, then no one has ever
downloaded it. But I find that exceptionally hard to believe...

Looking back through the list archives I think you'd find this comes up
at least every few months.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Index corruption
Next
From: Andrew Dunstan
Date:
Subject: Re: Instability in TRUNCATE regression test