I know we can
INSERT INTO "Table1" VALUES(X'57A00F3015310D4081AD4ADEF3EBDB5E');
But this little endian format is difficult to compare to the original Guid
300FA057-3115-400D-81AD-4ADEF3EBDB5E
How to use the original Guid in the SQL statement instead of the little endian one?
I'm having similar frustrations and am experimenting with a querying tool to do conversion for me.
For now I get by with something like the below.
Which returns
Formatting the original guid and comparing to the above:
I can get away with querying a partial Guid for filtering purposes.
Note % on the right side too - value is quoted
Try this:
I always do in this way, didn't find any problem.
If you want to easily compare to the original without converting then store it as text. It'll take more storage space and will be slower to read/write/compare, but it'll be more human readable.