2 ms·
I speak from bitter experience - UUID for PKs is not a good idea out of the box. Both writing as well as reading took very significant penalties. I did not desi
by mdekkers 5y ago
I speak from bitter experience - UUID for PKs is not a good idea out of the box. Both writing as well as reading took very significant penalties. I did not design that particular system, but I had to figure out why relatively simple queries took minutes to return.
- traceroute66 5y ago> I did not design that particular system ... why relatively simple queries took minutes to return The road of databases is paved with many such bodies. Whether it is developers treating databases like some blackbox dumping ground, or designing generic "portable" schemas, or people who don't know SQL writing weird long convoluted queries. Many people are quick to blame "the database", but 99% of the time its the fault of those who designed the schema and/or the queries that run on it. I think your statement "UUID for PKs is not a good idea out of the box" is unfair and too broad brush. Without knowing the exact details of every bit of your environment (from database hardware upwards), its not possible to accept such a generic statement to be read as a fact.