From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
---|---|
To: | "jerry(dot)evans(at)chordia" <jerry(dot)evans(at)chordia(dot)co(dot)uk> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Analogue to SQL Server UniqueIdentifier? |
Date: | 2008-02-18 16:52:04 |
Message-ID: | 20080218115204.c3f28b4e.wmoran@potentialtech.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In response to "jerry(dot)evans(at)chordia" <jerry(dot)evans(at)chordia(dot)co(dot)uk>:
> Hi
>
> My porting experiment has encountered the SQL Server UniqueIdentifier problem. I can see one or two suggestions about this have been made over the years but I'd like to try and stay close to the original. So:
>
> I'm wondering if I can use a combination of a domain 'hack' for syntatic compatibillity and an externally implemented function to handle generation.
>
> More specifically, given a table defined thus:
>
> CREATE TABLE jazz(
> UUID UniqueIdentifier DEFAULT newIdentifier(),
> rootname VARCHAR(255),
> data_source VARCHAR(1024),
> date_created DATETIME DEFAULT GETDATE())
>
> 1. Can I handle the UniqueIdentifier datatype via a domain that aliases UniqueIdentifier to char(X) (for example) ? This seems to work fine for the DATETIME datatype.
> 2. Implement newIdentifier() in some extension DLL that simply calls CoCreateGUID() ?
>
> or does uuid-ossp do this for me?
I'm no expert on this topic, but since nobody else has responded ...
I'm unsure why you would do anything other than install uuid-ossp.
Anything else is going to be a hack, and uuid-ossp was created specifically
to address this requirement.
Unless, of course, I've misunderstood your question.
--
Bill Moran
http://www.potentialtech.com
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2008-02-18 17:01:22 | Re: Analogue to SQL Server UniqueIdentifier? |
Previous Message | Andrew Sullivan | 2008-02-18 16:40:51 | Re: nntp interface not working? |