| From: | Jim Nasby <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Thomas Hallgren <thomas(at)tada(dot)se> |
| Cc: | Greg Stark <gsstark(at)mit(dot)edu>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] UUID's as primary keys |
| Date: | 2006-07-08 21:54:26 |
| Message-ID: | 5A5C5031-BE8D-474D-96BF-4374A420D881@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Jul 6, 2006, at 4:02 PM, Thomas Hallgren wrote:
>> In answer to your question, though my opinion carries no special
>> weight at
>> all, I would suggest adding a bare bones 16-byte data type to core
>> and a
>> second binary-compatible data type based on it that parsed/output
>> as uuids.
>> The extended uuid libraries should only go in pgfoundry/contrib.
> I second that.
+1. If there's enough user demand we can look at adding the type to
core (I don't see any real advantage to contrib over pgFoundry for
this). I'm not sure if it makes sense to add a generic 16 byte RAW to
core, either. I'd *much* rather see effort expended on a generic RAW
type which had it's size defined as part of the type and didn't use
varlena.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2006-07-09 03:12:37 | Re: [GENERAL] UUID's as primary keys |
| Previous Message | lanczos | 2006-07-08 19:02:04 | RE: migration from Sybase to Postgres |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2006-07-08 22:16:10 | Const warnings in psql |
| Previous Message | Jim Nasby | 2006-07-08 21:47:33 | Re: lastval exposes information that currval does not |