2 ms·
These things sound like they'd be true of environments with dysfunctional or naive RDBMS practices. While it may not be true for inexperienced developers, an e
by gdulli 11y ago
These things sound like they'd be true of environments with dysfunctional or naive RDBMS practices.
While it may not be true for inexperienced developers, an experienced developer can assume proper index use (because it's part of their responsibility to ensure or implement) and has access to sufficient heuristics about how a query will perform. And when it should and shouldn't be assumed to be predictable. (Again, informed by experience.)
If you only know the ORM layer, which is unfortunately becoming more common, of course you don't have the full picture and can't make proper decisions.
- andybak 11y ago> If you only know the ORM layer If you're using an ORM and you have to care about performance then this might be a necessary skill. However - there are very few times I've really had to do this. Usually either performance isn't a concern or there's a simpler solution than painstaking analysis of SQL query plans - de-normalize, cache or write smarter ORM code.