From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | Michael Gould <mgould(at)intermodalsoftwaresolutions(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Full GUID support |
Date: | 2011-07-03 21:02:36 |
Message-ID: | 4081.1309726956@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dave Page <dpage(at)pgadmin(dot)org> writes:
> Even If that weren't the case, integrating the type wouldn't fix the
> problem anyway, unless you're suggesting we implement our own UUID
> generator (which isn't nearly as straightforward as it might seem, as
> I understand it)..
Yeah. If there were One True Way to create a UUID, I would probably
agree that we should push that functionality into core. But there are
a lot of ways (and the reason for that is that they all suck in one
fashion or another :-(). Between that and the lack of portability of
many of the better ways, this is something I'm happy to keep at arm's
length.
Michael: this is something that was discussed before, when we agreed
to put the uuid type but not the generator functions in core. See
the archives. Nothing about the situation has changed since then.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Brar Piening | 2011-07-03 21:14:31 | Re: %ENV warnings during builds |
Previous Message | Dave Page | 2011-07-03 20:40:12 | Re: Full GUID support |