Re: UUID/GUID discussion leading to request for hexstring bytea?
| От | mark@mark.mielke.cc |
|---|---|
| Тема | Re: UUID/GUID discussion leading to request for hexstring bytea? |
| Дата | |
| Msg-id | 20060918161417.GA31239@mark.mielke.cc обсуждение |
| Ответ на | Re: UUID/GUID discussion leading to request for hexstring bytea? (Gevik Babakhani <pgdev@xs4all.nl>) |
| Ответы |
Re: UUID/GUID discussion leading to request for hexstring bytea?
|
| Список | pgsql-hackers |
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.
Gevik: Once you have your patch in a ready state, I'll compare it
against what I have and see if there is anything missing, or if I
did anything better. Possibly not, but it's worth the check.
Cheers,
mark
--
mark@mielke.cc / markm@ncf.ca / markm@nortel.com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all and in the darkness
bindthem...
http://mark.mielke.cc/
В списке pgsql-hackers по дате отправления: