[EMAIL PROTECTED] 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 sor
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 fo
> 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.
--
Gevik Babakhani wrote:
LIKE could come handy if someone wants to abuse the uuid datatype to
store MD5 hash values. However I am not going to implement it if there
is no need for that (assuming it will pass the acceptance test)
Perhaps providing LIKE just to encourage abuse is not such a good
LIKE could come handy if someone wants to abuse the uuid datatype to
store MD5 hash values. However I am not going to implement it if there
is no need for that (assuming it will pass the acceptance test)
On Mon, 2006-09-18 at 10:06 +0200, Thomas Hallgren wrote:
> Gevik Babakhani wrote:
> > To my
Gevik Babakhani wrote:
To my opinion GUIDs type need to provide the following in the database.
1. GUID type must accept the correct string format(s), with of without
extra '-'
2. GUID type must internally be stored as small as possible.
3. GUID type must be comparable with == , != , LIKE and (N
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.
> 4. GUID type must have the ability to be indexed, grouped, ordered,
> DI
On Wed, 2006-09-06 at 17:05 -0400, [EMAIL PROTECTED] wrote:
> The UUID type itself has value, however, the value it provides is
> limited. Generation of a UUID doesn't have to occur with the database.
> The application inserting the row can generate the UUID. The UUID type
> itself has limited val
