3 ms·
Databases tend to be "stickier" than other parts of any large software system. Largely because database migrations are costly. You can't just tear down an old d
by yen223 2y ago
Databases tend to be "stickier" than other parts of any large software system. Largely because database migrations are costly. You can't just tear down an old database and rebuild a new one, you have to figure out how to move all that data across too.
The consequence is that things in database-land tends to move slower than other types of software. This I think is the major reason why we still use SQL.
- polishdude20 2y agoWhat's the SQL alternative?
- p10_user 2y agoJSON - er JSON-based document storage - documents with unique identifiers. and the ability to define and set schemas for the JSON, and ... we're back to a relational database
- ogogmad 2y agoI think he was talking about the query language.
- aitchnyu 2y agoHopefully Edgedb. It could make most ORMs and heavyweight web frameworks redundant, maybe some BI tools and jobs too. https://www.edgedb.com/ https://www.edgedb.com/
- adhamsalama 2y agoLooks kind of like PRQL https://github.com/PRQL/prql https://github.com/PRQL/prql
- jart 2y agoHave postgres updates actually been requiring users do migrations? Or is this just a fear that something will go wrong?
- bc_programming 2y agoWell if it's self-hosted you have to do it yourself. You can either backup your databases from the old version and restore it to the new version once installed, or you can use pg_upgrade to upgrade/copy a old version data directory to the new version. I don't think this is done automatically when you simply install a new postgres version, but I'm not certain of that.
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]
- magicalhippo 2y agoFrom what I can gather, yes[1]: A dump/reload of the database or use of the pg_upgrade application is required for major upgrades. Now, seems one can mostly use pg_upgrade, which only rewrites the system tables[2] so is fairly quick. But if on-disk format has changed it seems you're forced to dump and reload. At work we've mainly been using SQLAnywhere, which would just disable new functionality for databases using old on-disk format. So upgrading major versions has usually been fairly painless and quick. [1]: https://www.postgresql.org/support/versioning/ https://www.postgresql.org/support/versioning/ [2]: https://www.postgresql.org/docs/current/pgupgrade.html https://www.postgresql.org/docs/current/pgupgrade.html