News for hackers. Stuff that matters.

A comment on Unexpected downsides of UUID keys in PostgreSQL. Parent comment

Re:Unexpected downsides of UUID keys in PostgreSQL by totalhack on Thursday June 22, 2023 @08:37AM (#36431207)
You can incorrectly join on any columns you want. That's not really the fault of the column types IMO, that's a problem in the layers above.
[ Parent | on HN ]
Re:Unexpected downsides of UUID keys in PostgreSQL by dpcx on Thursday June 22, 2023 @08:46AM (#36431297)
True, but you can't incorrectly join on UUID due to its anti-collision nature.
[ Parent | on HN ]
Re:Unexpected downsides of UUID keys in PostgreSQL by ibash on Thursday June 22, 2023 @11:18AM (#36433472)
Yes you can, you’ll not get the correct result set.
[ Parent | on HN ]
Re:Unexpected downsides of UUID keys in PostgreSQL by OJFord on Thursday June 22, 2023 @02:48PM (#36436907)
As sibling says, you can make exactly the same mistake and it not colliding just means no join - but if it's an outer join and one of many joins or in a nested query it might not be immediately obvious it's happened, or what the issue is even if it is.
[ Parent | on HN ]