I agree with Josh on the UUID type, it gets abused far too often and (IMHO) isn't widely enough used to belong in the core. Couldn't you just fix the problem in pguuid rather than write a whole new type?
> 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
---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
