| From: | Thomas Hallgren <thomas(at)tada(dot)se> |
|---|---|
| To: | Psql_General <pgsql-general(at)postgresql(dot)org> |
| Subject: | UUID's as primary keys |
| Date: | 2006-06-28 07:01:49 |
| Message-ID: | 44A2295D.7000709@tada.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
I'm building an app where I have several entities that are identified
using a UUID (i.e. a 128 bit quantity). My current implementation uses a
composite primary key consisting of two int8 values. It's a bit
cumbersome and I would much rather have a distinct type. An earlier
implementation using Oracle mapped the UUID to a RAW(16) but PostgreSQL
doesn't have that and the BYTEA adds extra overhead.
What would be the best (as in most efficient) mapping for a 128 bit
primary key?
Regards,
Thomas Hallgren
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2006-06-28 07:13:06 | Re: UUID's as primary keys |
| Previous Message | Tim Allen | 2006-06-28 01:42:03 | Re: TSearch vs. Homebrew |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2006-06-28 07:13:06 | Re: UUID's as primary keys |
| Previous Message | Tom Lane | 2006-06-28 04:53:44 | Re: Page format changes for 8.2? |