From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: pgsql-hackers@postgresql.org
Subject: Re: uuid type for postgres
Date: Tue, 6 Sep 2005 10:02:43 -0700
User-Agent: KMail/1.8
Cc: mark@mark.mielke.cc, nathan wagner <nw@hydaspes.if.org>
References: <20050906135057.GA24136@granicus.if.org>
	<20050906144930.GA27641@mark.mielke.cc>
In-Reply-To: <20050906144930.GA27641@mark.mielke.cc>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200509061002.43803.josh@agliodbs.com>

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 arguments.   

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 using 
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.

-- 
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco