From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Gevik Babakhani <pgdev(at)xs4all(dot)nl> |
Cc: | mark(at)mark(dot)mielke(dot)cc, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: UUID/GUID discussion leading to request for hexstring bytea? |
Date: | 2006-09-07 12:46:36 |
Message-ID: | 20060907124636.GM10093@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Sep 07, 2006 at 01:27:21PM +0200, Gevik Babakhani wrote:
> To my opinion only some of relational/compare operations like == and !=
> apply to such values. comparing guid >= guid or md5 < md5 is also
> meaningless.
<snip>
> 4. GUID type must have the ability to be indexed, grouped, ordered,
> DISTINCT... but not MAX(), MIN() or SUM()....
Err, for "ordered" you need to define <, >, >=, <=, which means you're
going to get MAX, and MIN for free...
> I also think we should have the GUID/UUID as a datatype and not just
> functions handling hexstring.
Sure, but that will be the I/O format, right?
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Moran | 2006-09-07 12:48:35 | Re: [PATCHES] Template0 age is increasing speedily. |
Previous Message | Martijn van Oosterhout | 2006-09-07 12:41:02 | Re: Fixed length data types issue |