PostgreSQL and UUID as Primary Key

Re:PostgreSQL and UUID as Primary Key by rangerelf on Friday July 05, 2024 @06:34PM (#40886645)

I read your post and hear echoes of "Who would ever need more than 2 digits for the year in this timestamp column?"

Never again.

[ Parent | on HN ]

Re:PostgreSQL and UUID as Primary Key by vbezhenar on Friday July 05, 2024 @06:45PM (#40886718)

Using 2 digits for year is as wrong as using 8 bytes for year.

[ Parent | on HN ]

Re:PostgreSQL and UUID as Primary Key by riku_iki on Saturday July 06, 2024 @01:49AM (#40888405)

scale of damage is very different, so "as" is up to discussion.

[ Parent | on HN ]

Re:PostgreSQL and UUID as Primary Key by lazide on Saturday July 06, 2024 @09:54PM (#40894700)

Eh, using 2 digits for year is a lot ‘more wrong’ than 8 bytes. Since all (current) known use cases can fit in 8 bytes for the conceivable lifespan of human civilization.

2 digit years don’t even support the use case of ‘store the current year’ fully.

[ Parent | on HN ]

Re:PostgreSQL and UUID as Primary Key by rangerelf on Monday July 08, 2024 @02:57PM (#40908259)

Don't wake me up when year 9,223,372,036,854,775,807 rolls by please.

[ Parent | on HN ]