| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | Thomas Hallgren <thomas(at)tada(dot)se>, mark(at)mark(dot)mielke(dot)cc, Andrew Dunstan <andrew(at)dunslane(dot)net>, "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fixed length datatypes. WAS [GENERAL] UUID's as |
| Date: | 2006-06-30 06:27:10 |
| Message-ID: | 44A4C43E.7090503@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Jim,
> I agree about splitting the utilities, except that I think the database
> should be able to generate UUIDs somehow.
There is a GUID add-in, and someone is working on a 2nd one. UUIDs are
not part of the SQL standard, and we've only seen sporadic demand for
them (and different types each time) so I can't imagine one making it
further than contrib real soon.
Also, one could argue that UUIDs are a foot gun, so they're not exactly
the type of thing we want to advocate in advance of demand.
--Josh Berkus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alain Roger | 2006-06-30 06:28:24 | phppgadmin |
| Previous Message | Bruno Wolff III | 2006-06-30 04:53:47 | Re: Strange Behavior with Serializable Transcations |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Hallgren | 2006-06-30 06:53:28 | Re: Fixed length datatypes. WAS [GENERAL] UUID's as |
| Previous Message | Tom Lane | 2006-06-30 03:25:16 | Re: Index corruption |