9 ms·
It seems your requirements mostly center around OLAP use cases? In that case, an ORM isn't the right tool to begin with, i.e. lacking support for these things d
by gunnarmorling 4y ago
It seems your requirements mostly center around OLAP use cases? In that case, an ORM isn't the right tool to begin with, i.e. lacking support for these things doesn't diminish the value proposition of ORMs, which lies elsewhere (mapping results to managed object graphs in OLTP applications, tracking changes to the same, and synching them efficiently back to the DB). For OLAP, object mapping typically doesn't provide much value.
- ttfkam 4y agoNope, I'm mostly OLTP. But even mostly OLTP systems need dashboards, even if they're read from periodically refreshed materialized views. I also use things like lateral unnest of arrays for ordering dependent rows. Actually LATERAL shows up a lot to compute on the fly. And while everything I listed can and should be used in OLAP, OLTP has uses for these items too.