From: | Thomas Hallgren <thomas(at)tada(dot)se> |
---|---|
To: | mark(at)mark(dot)mielke(dot)cc |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: UUID/GUID discussion leading to request for hexstring bytea? |
Date: | 2006-09-18 16:23:36 |
Message-ID: | 450EC808.20708@tada.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
mark(at)mark(dot)mielke(dot)cc wrote:
> On Mon, Sep 18, 2006 at 11:12:54AM +0200, Gevik Babakhani wrote:
>>> Magnitude comparison on the GUID as a whole makes no
>>> sense to me.
>> I agree. Any kind of comparison except equality has no meaning for the
>> GUID. (And this is discussed before) I rather have the option to sort
>> and group for the sake of consistency and compatibility.
>
> Thomas: The ability to sort / comparison is required for use with
> B-Tree index. I prefer a fast comparison over one with more meaning.
> memcmp() is fine with me and it is how I implement it in my UUID
> PostgreSQL library.
>
Fair enough. Although the magnitudes as such makes little sense, the ability to order will
make it possible to compare results from different queries etc. Very difficult to do with
random order.
Regards,
Thomas Hallgren
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-09-18 16:52:18 | Re: OID conflicts |
Previous Message | mark | 2006-09-18 16:23:16 | Re: [HACKERS] Patch for UUID datatype (beta) |