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: Wed, 7 Sep 2005 11:47:23 -0700
Message-ID: <914AC2C5-A81F-415B-B5AC-832A22D12ECB@redivi.com> (raw)
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>
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
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 using the --to and --cc options:
reply via email
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: <914AC2C5-A81F-415B-B5AC-832A22D12ECB@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