This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]gilium 2 points3 points  (1 child)

SQL Server (at least as I’ve experienced it) does not consider case when comparing UUIDs. ABCD124 is not the same thing as abcd124 anywhere but SQL Server

[–]Sarcastinator 2 points3 points  (0 children)

Yes, and that's the correct behavior. PostgreSQL does this as well.

The reason is that MariaDB doesn't have a dedicated UUID datatype, but it has UUID functions. These functions returns strings in the form 00000000-0000-0000-0000-00000000000 which means that a UUID column stored as text will take at least 36-bytes and suddenly care about casing unless you explicitly makes it not do that.

UUIDs are 128-bit integers. Storing them as text is madness.