Skip site navigation (1) Skip section navigation (2)

Re: guid/uuid datatype

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Gevik Babakhani <pgdev(at)xs4all(dot)nl>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org, Neil Conway <neilc(at)samurai(dot)com>
Subject: Re: guid/uuid datatype
Date: 2007-01-20 11:19:59
Message-ID: 45B1FADF.8040800@hagander.net (view raw or flat)
Thread:
Lists: pgsql-patches
Gevik Babakhani wrote:
>> I'd be willing to accept a core uuid type sans generator function,
>> but is that really all that useful?
>>
>  This is also a point I remember from the last discussions. To not to
> include the generator in the core. The generation of the uuid is then
> going to be on the client side.
> 
> The uuid type is very useful, especially when migrating from other
> systems to pg  (ms->pg or syb->pg).

But does it really help if you don't have the generator?

I don't use UUIDs much myself, but I think in all cases I've seen that
use the uuid type in SQL Server they're also using the generator function.
Those that just store UUIDs in the database often just uses varchar - in
order to be more portable, I guess.

Not saying it wouldn't be good to have uuid for portability, I'm just a
bit unsure of how much use it is without a generator function...

//Magnus

In response to

Responses

pgsql-patches by date

Next:From: Gevik BabakhaniDate: 2007-01-20 11:59:40
Subject: Re: guid/uuid datatype
Previous:From: Magnus HaganderDate: 2007-01-20 11:17:04
Subject: Re: O_DIRECT support for Windows

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group