| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | 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:15:45 |
| Message-ID: | 20070120121545.GM26080@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
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.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Kaltenbrunner | 2007-01-20 12:38:46 | Re: guid/uuid datatype |
| Previous Message | Gevik Babakhani | 2007-01-20 11:59:40 | Re: guid/uuid datatype |