Hey, good one Raul, I didn't see that coming. Good question!

regards
Mario

Raul,

<< Are you planning to surface an ability to query this directly using SQL ?
(would need some text to binary conversion/cast functions or ability to
specify hex valued for binary). >>

That may have been the initial hold-up.  But, to answer your question,
yes, one would need to either use a CAST() for GUID string constants in
order to do comparisons, or use a straight-up binary (hex) constant for the
comparisons.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<< But, to answer your question, yes, one would need to either use a CAST() for GUID string constants in
order to do comparisons, or use a straight-up binary (hex) constant for the
comparisons.
If you have any other questions, please let me know.
>>

Thanks - I'm sure you're already covering both sides of this but will ask just in case that we'll be able to cast both ways : cast binary to text guid/hex value (as part of select fields for example)  and reverse cast from text/hex to binary to use in where clause or such.

Raul

Raul,

<< Thanks - I'm sure you're already covering both sides of this but will ask
just in case that we'll be able to cast both ways : cast binary to text
guid/hex value (as part of select fields for example)  and reverse cast from
text/hex to binary to use in where clause or such. >>

Yes, CAST() works that way now (for binary).

I'm pretty sure that I'm going to have to introduce a new SQL type,
something like BGUID that will be a sub-type of a BYTE type, as opposed to
the GUID type, which is a sub-type of the CHAR type.

Tim Young
Elevate Software
www.elevatesoft.com