| From: | Horst Herb <hherb(at)malleenet(dot)net(dot)au> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: GUID in postgres |
| Date: | 2001-10-25 03:53:27 |
| Message-ID: | 20011025034926.30847.qmail@gnumed.dhs.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-sql |
On Thursday 25 October 2001 03:41, John Hasler wrote:
> Josh writes:
> > I'm sure you could make your own GUID, whatever one is.
>
> Globally Unique IDentifier, probably. Just hash a 128 bit random number
> with the current date.
That gives you no gurantee it will be unique.
What we are using is the following:
- All tables in need of a global ID _within_ a database inherit a globid
table which contains nothing but an ID of type serial.
- When we need cross-database unique IDs within the same system, the globid
table contains a database identifier as well (like the OID of the pg_database
entry for the database).
Horst
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-10-25 04:41:36 | Re: Disable Transaction - plans ? |
| Previous Message | Bruce Momjian | 2001-10-25 03:50:06 | Re: Disable Transaction - plans ? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Hasler | 2001-10-25 12:33:04 | Re: GUID in postgres |
| Previous Message | Stephan Szabo | 2001-10-24 21:55:05 | Re: dropping foreign key |