| I work as part of building an RDBMS, but most importantly, I know how people misuse RDBMS for more than +20 years. People write terrible schemas. ORMs hide complexities and make terrible queries. Some people refuse to use sophisticated features like DataTime types for storing DateTypes (using String instead. I'm not talking about formatting!). Also, neither use JOINS or VIEWS or FUNCTIONS, or even adding indexes. They build MonDB schemas on top of PostgreSQL. And then build their own query engine, that is not like the one an RDBMS is happy to deal it. In short: "Trash-in Trash-out" but for queries, and that is something will be triggered by a system like this. Plus: Query engine optimizations IS the HARDEST aspect of build a DB:
Example: https://db.in.tum.de/~radke/papers/hugejoins.pdf > The largest real-world query that we are aware of accesses more than 4,000 relations. And you have a lot of constraints: - More indexes more data, less RAM, less SPACE. - More indexes, more query optimization paths, more complex solving of query optimization - Adding more indexes could create suboptimal access patterns. - And that changes with time - And that changes could be on a second
- And then you can create an unintentional delay that WILL impact the pocket of somebody Doing this stuff "silently" is a sure way to add problems that will be very hard to solve or debug. Sure, without this some of the problems still remain, but at least will be possible to see why and to know when it get solved. If anyone manages to create a solid implementation of this, it will deserve a noble prize, an oscar, a place in the half of fame, and will be rich. |