3 ms·
IMO your use case would suit only very static needs that maybe you should consider using a completely different thing than a SQL database. I see the abstraction
by TomMarius 8y ago
IMO your use case would suit only very static needs that maybe you should consider using a completely different thing than a SQL database. I see the abstraction you're talking about as unnecessary as the whole point - and while it's true that an optional feature that would let you do that could be nice, I fail to see any point of that.
- lixtra 8y agoIf my desire is so wrong, why do things like index hints exist? And the very static case is the easy one in OLAP. You build a star schema that is so simple that the planner could not get it wrong. To fill this schema you use some ETL tool that very much resembles a static plan. In the dynamic, exploratory phase (does it make sense to look at the data this way) you have to deal with the nasty complicated queries.
- hobs 8y ago"So simple the planner could not get it wrong" - and then you add a billion rows, or the business needs schema changes, or, or, or... If you want to have that exact behavior I'd agree with the gp, we are talking about data access, but not all data access has to be a SQL database. Index hints are just that, hints, they are not commands - because there are tipping points that they just dont make sense anymore.