In-Reply-To: <20050907170430.GA6281@granicus.if.org>
References: <20050906135057.GA24136@granicus.if.org>
	<7CDBCE29-55BE-4EE3-8868-F50DB1E914F6@refractions.net>
	<20050907051508.GA3572@granicus.if.org>
	<200509070945.17916.josh@agliodbs.com>
	<20050907170430.GA6281@granicus.if.org>
Mime-Version: 1.0 (Apple Message framework v734)
Message-Id: <914AC2C5-A81F-415B-B5AC-832A22D12ECB@redivi.com>
Cc: pgsql-hackers@postgresql.org
From: Bob Ippolito <bob@redivi.com>
Date: Wed, 7 Sep 2005 11:47:23 -0700
To: nathan wagner <nw@hydaspes.if.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: uuid type for postgres

On Sep 7, 2005, at 10:04 AM, nathan wagner wrote:

> On Wed, Sep 07, 2005 at 09:45:17AM -0700, josh@agliodbs.com wrote:
>
>
>> I think the issue is portability.  Remember that this type needs  
>> to work on
>> Windows as well as all POSIX platforms and AIX.
>>
>
> I had forgotten about windows.  I'll see to what extent the library  
> i'm
> using is portable to windows.

You don't need to use a non-standard library for a lot of platforms,  
you're pretty much guaranteed UUID support for (at least):
Linux/Darwin/Mac OS X: uuid_generate <uuid/uuid.h> (part of libc, at  
least on Darwin)
FreeBSD: uuid_create <uuid.h> (again, libc)
Windows: UuidCreate <Rpc.h> (link to Rpcrt4.dll, IIRC)

Where a native UUID generate is not available, you can include some  
implementation, but surely other platforms also include UUID  
implementations.

I think Windows portability is a non-issue here.

-bob