this post was submitted on 03 Aug 2024
12 points (100.0% liked)
PostgreSQL
652 readers
1 users here now
The world's most advanced open source relational database
Project
- About (history)
- Docs
- Donate to PostgreSQL
- Wiki
- Planet PostgreSQL
- IRC
- Mailing lists:
- pgsql-announce
- pgsql-hackers (developers)
- pgsql-general
- pgsql-jobs
- User Groups
Events
- SEAPUG Summer BBQ, 6 July in Seattle
- SFBA PostgreSQL Meetup, 12 July
- Chicago PostgreSQL Meetup, 19 July
- PGDay UK 2023, 12 September in London
- PGConf 2023, 3-5 October in New York City
- PGDay Israel 2023, 19 October
- PGConf.EU 2023, 12-15 December in Prague
Podcasts
Related Fediverse communities
- c/SQL on programming.dev
- #sql on Mastodon
- #postgresql on Mastodon
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I feel like a lot of the complication of this story was from using rails to try and develop the implementation of adding a primary key to the database.
Initially testing via SQL would've quickly blown through the
null
anddefault
requirements, after which it's just translating into whatever ORM you are using, testing and deploying.I know a lot of ORMs make it super easy to quicky add a migration in a language you already know well. But primary keys are pretty core to tables, and probably something assumed to be set up when first creating the table (ie rails did auto-magick with the new
id
column).