Re: guid/uuid datatype

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Magnus Hagander <magnus(at)hagander(dot)net>, Gevik Babakhani <pgdev(at)xs4all(dot)nl>, 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 12:38:46
Message-ID: 45B20D56.3010206@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Alvaro Herrera wrote:
> Magnus Hagander wrote:
>> 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?
>
> We could have all the type code in core, and the generator in contrib or
> pgfoundry. That way the user can choose the most appropriate generator,
> even if it's platform-specific. Or he can choose to use a client-side
> generator.

that seems like a good compromise - have the type in core and generators
in contrib/pgfoundry. In one or two releases we might see some feedback
on the portability and how people use those and could decide on leaving
it that way or move the generators into core as well.

Stefan

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Peter Eisentraut 2007-01-20 13:07:21 Re: guid/uuid datatype
Previous Message Alvaro Herrera 2007-01-20 12:15:45 Re: guid/uuid datatype