>Of course they wouldn't match. I didn't sacrifice any bytes of the 16. Your version sacrifies half of the bytes (some bytes might be but not all IMHO) then does a hex+endian conversion.
>On the same GUID value (after call to uuidcreate) apply str from guid and you'd see what I mean.
>Cetin

I've checked out database. All PK/FK fields are character, not character binary. I assume they can not take these chars then.