News for hackers. Stuff that matters.
Re:When to Avoid JSONB in a PostgreSQL Schema by teraflop on Thursday September 01, 2016 @10:55PM (#12410508)
"I might want to add more columns later" is not a good justification for avoiding a relational model. If you realize that you want an additional column, just run an ALTER TABLE statement.
Re:When to Avoid JSONB in a PostgreSQL Schema by knucklesandwich on Thursday September 01, 2016 @11:02PM (#12410535)
Totally agreed. Some people have an unreasonable fear of migrations (not to try to put words in the above poster's mouth, just pointing out something that I've noticed). You generally shouldn't worry about migration-related downtime with Postgres if you're not using table constraints, using columns with defaults, or changing a column's type. There are very few migration procedures that require something like a table rewrite these days, or even an index rebuild.
Re:When to Avoid JSONB in a PostgreSQL Schema by collyw on Friday September 02, 2016 @07:10AM (#12412195)
Migrations are a pain in the arse. But not as much as trying to maintain a "schemaless" app.