22 ms·
Sure, my point is that RDBMS are not better they are different. Right tool for the job an' all that.
by gaius 10y ago
Sure, my point is that RDBMS are not better they are different. Right tool for the job an' all that.
- dragonwriter 10y ago> Sure, my point is that RDBMS are not better they are different. I can't see any way in which the relational model, either abstractly in or practical application, is less suited to any task than the hierarchical model, and its clearly better suited for many tasks. Its both different and better. The hierarchical model is, especially given the alternatives that existed at the time, good enough for some tasks, sure. There are alternative models that are better suited for some tasks (e.g., graph model), at least on a pragmatic level, but I don't see that the hierarchical model is one of them.
- gaius 10y agoYou can do hierarchical queries in Oracle and now you can in Postgres too[1], but that's a relatively recent innovation and it's still horrible in MySQL[2] IMS is still a huge seller for IBM and a tiny fraction is periodically reinvented and hyped as the latest and greatest thing (e.g. MongoDB) so there are use cases for which it is still the right tool. I feel dirty for saying "MongoDB" and "right tool" in the same sentence. [1] http://stackoverflow.com/q/24898681/447514 http://stackoverflow.com/q/24898681/447514 [2] http://stackoverflow.com/q/7631048/447514 http://stackoverflow.com/q/7631048/447514
- tracker1 10y agoThere's always RethinkDB as probably a better example... I don't really dislike MongoDB, I've used it, aware of its' issues, and liked it. I just find RethinkDB's approach much more sane.
- tracker1 10y agoWhen a normalized entity for real world display and manipulation requires over 30 join operations for a single record and children. Or requires lookup tables (db anti-pattern) in order to keep the number of tables in the schema reasonable. JOINS kill db performance at scale, enough said. This is why document, object, key/value, column and other types of database stores have become very popular in the past decade, precisely because relational RDBMS aren't a good fit, or even good enough in many cases. Don't get me wrong, I'd be much more inclined to use a relational/sql RDBMS in many cases. That doesn't mean they are better in even half the cases.