From: | Gevik Babakhani <pgdev(at)xs4all(dot)nl> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
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 |
Date: | 2006-09-07 13:35:59 |
Message-ID: | 1157636159.614.12.camel@voyager.truesoftware.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 2006-09-07 at 14:46 +0200, Martijn van Oosterhout wrote:
> 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...
>
Yes indeed, I just want to address that guid > guid or any other
operation like that has no meaning.
> > 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?
Yes, I/O format as part of the datatype and not a separate function.
>
> Have a nice day,
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-09-07 14:27:25 | Re: Fixed length data types issue |
Previous Message | Merlin Moncure | 2006-09-07 13:04:24 | Re: [HACKERS] Template0 age is increasing speedily. |