Avoid UUIDv4 Primary Keys

Re:Avoid UUIDv4 Primary Keys by groundzeros2015 on Monday December 15, 2025 @10:59AM (#46276178)

You can’t design something by trying to anticipate all future changes. things will change and break.

In my personal design sense, I have found keeping away generality actually helps my code last longer (based on more concrete ideas) and easier to change when those days come.

[ Parent | on HN ]

Re:Avoid UUIDv4 Primary Keys by dpark on Monday December 15, 2025 @12:26PM (#46277469)

In my experience, virtually every time I bake concrete data into identifiers I end up regretting it. This isn’t a case of trying to predict all possible future changes. It’s a case of trying to not repeat the exact same mistake again.

[ Parent | on HN ]

Re:Avoid UUIDv4 Primary Keys by groundzeros2015 on Monday December 15, 2025 @03:33PM (#46280197)

I don’t disagree with that, I’m disagreeing with this comment that we can’t make protocol or data decisions that might change.

[ Parent | on HN ]

Re:Avoid UUIDv4 Primary Keys by dpark on Monday December 15, 2025 @03:56PM (#46280531)

I misunderstood then. I interpreted your comment to say that you eschew generalization (e.g. uuids) in favor of concrete data (e.g. names, email addresses) for ids in your designs.

[ Parent | on HN ]