4 ms·
It bothers me a bit why the author never mentioned what is the right data type to use instead of varchar(36). I had to google it up to know there is a data typ
by max23_ 9y ago
It bothers me a bit why the author never mentioned what is the right data type to use instead of varchar(36).
I had to google it up to know there is a data type for GUID called "uniqueidentifier" (MS SQL) or "uuid" (PostgreSQL). As for MySQL, there is no such equivalent and suggestion is to use CHAR(38) instead.
Does that mean MySQL will have to live with the 9x cost in size issue?