4 ms·
Because RDBMSes are still an unsolved problem, and new features keep coming along that are actually very useful but not easy to standardize.
by paperplatter 2y ago
Because RDBMSes are still an unsolved problem, and new features keep coming along that are actually very useful but not easy to standardize.
- taeric 2y agoAnd if I'm doing advanced queries, I largely sympathize. Basic group by and such, though? I get why cube and roll-up aren't always there, maybe. The rest, though? If I was demanding equivalent speed, it would be one thing. I am fine needing an integration environment for that. I only want a test environment to show queries return as expected. Is also good documentation for reporting focused queries.
- paperplatter 2y agoIf you're doing very basic things, the same exact syntax will probably work on multiple. But even then, implementation details like isolation level come into play.
- taeric 2y agoLately, it was usually the abysmal state of aggregate functions that bit me. That and wanting to use "with" to make readable sql. I really should just change my main complaint to be that most options should have an easy to setup and tear down local equivalent for testing.
- paperplatter 2y agoI feel that. Postgres has dump/restore at least, though that's less portable than a unit testing fake. And the thing I use at work lacks a dump/restore feature somehow :/