From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | mark(at)mark(dot)mielke(dot)cc, nathan wagner <nw(at)hydaspes(dot)if(dot)org> |
Subject: | Re: uuid type for postgres |
Date: | 2005-09-06 17:02:43 |
Message-ID: | 200509061002.43803.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
Mark,
> I suggest that UUID be recommended in place of SERIAL for certain
> classes of applications, and that it therefore belongs in the core.
> UUID and SERIAL can be used together (although, once you have a UUID,
> it may not be useful to also have a SERIAL).
I think that, if you want to push a refactored UUID type for PostgreSQL
8.2, that you'd better separate your database design arguments from your
inclusion arguments.
For example, you might get my agreement that it would be useful to have a
UUID as a core type; you would *never* get my agreement to recommend using
UUID to newbies. I have seen *far* too many abuses of UUIDs in really
bad database design. People who use them should be experienced enough to
know what they're doing.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | nathan wagner | 2005-09-06 17:15:44 | Re: uuid type for postgres |
Previous Message | Alvaro Herrera | 2005-09-06 17:01:53 | Re: Mysteriously lost values in nodes |
From | Date | Subject | |
---|---|---|---|
Next Message | nathan wagner | 2005-09-06 17:15:44 | Re: uuid type for postgres |
Previous Message | Tom Lane | 2005-09-06 15:38:57 | Re: uuid type for postgres |