It would be amazing if it could display UUIDs. SQlite doesn't support them natively, but many people store them as binary blobs.
Jetbrains products realize that these binary values are UUIDs and let me edit them easily.
Jetbrains products realize that these binary values are UUIDs and let me edit them easily.
This is a bit of a shift, but the numbers aren't really stable yet so it's hard to tell if it'll stay there.
Too bad this is mac only. I mean, im a mac user (among other things) but i don't want to depend on platform specific tooling.
Both MariaDB and SQL Server have dedicated data types for UUIDs, and they sort in an unexpected order if you're unfamiliar with the structure of a UUID or the endianness of certain portions of it. Oracle assumes it's going to be binary, but the generating function SYS_GUID() has some endianness issues you can run into. Meanwhile, PostgreSQL kist sorts them like a string!
Similarly, if you're using .Net to generate a native GUID type and passing that through your RDBMS provider, it may arrive and be stored differently due to that endianness problem.
Expecting that every SQLite database is going to be storing UUIDs in an identical manner seems insane to me.
It's the fact that, as the Base author, you don't really know how a given application might present a 16-byte binary version of a UUID to the database. If you don't know that, how can you reverse it to display the correct string representation? There are complications with byte groups potentially being in different places, and even the potential of mixed byte ordering.
How can Base make a 16-byte binary format that display both a GUID stored from a .Net application from person A, and also a UUID from a Python application from person B, and have the string representation be accurate in both cases? I don't think you can.
A binary blob of 7-bit-clean ASCII still fits within a binary blob.