| From: | Gevik Babakhani <pgdev(at)xs4all(dot)nl> |
|---|---|
| To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, 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 |
| Subject: | Re: guid/uuid datatype |
| Date: | 2007-01-25 19:25:14 |
| Message-ID: | 1169753114.30038.3.camel@voyager.truesoftware.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
> I thought the consensus was to provide the only atatype initially and
> look into providing the generator functions later or via an external
> project (pgfoundry or contrib/).
This was my understanding too... to include the uuid in the core and let
the actual value be generated elsewhere...(client or separate
project)...
I do not think having a uuid datatype as contrib module separately will
do us much good. All professional dbs support this as built in. So why
shouldn't we...
Regards,
Gevik.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-01-25 19:38:45 | Re: setlocal to build.bat |
| Previous Message | Joshua D. Drake | 2007-01-25 18:35:00 | Re: guid/uuid datatype |