3 ms·
Are you really saying that people are too lazy to draw lines between tables in their database? Too lazy to right click a column name and click "Index"? That y
by jasonkester 16y ago
Are you really saying that people are too lazy to draw lines between tables in their database? Too lazy to right click a column name and click "Index"? That you wouldn't notice on your own that a particular query took four minutes to run and maybe open it up and poke around? That this should be something the database does for you???
That is not the hard part of my job. That is the easy part. No thank you.
- derefr 16y agoBut, as you say, it is part of your job. The difficulty, or ease, of the problem, has nothing to do with it; at some shops, it's nobody's job, and so it just doesn't get done. In 90% of shops, the last time anyone so much as glances at the database is to run the CREATE TABLE query. No one profiles, no one optimizes—you're lucky if anyone even declares any indexes (ahead of time, as a guess, of course.) And, consider: if it's the easy part, why are [some] people switching to NoSQL just to avoid doing it? ;)
- jasonkester 16y agoI think you misunderstood me. Part of writing the CREATE TABLE query you mention is hooking up primary and foreign keys and setting up indexes. That's just how you build databases. Even if you never look at it again, you still need to do it.
- kunley 16y agoI agree with your points and ideas of auto-optimization. I'd just replace "at some shops" with "at most shops" to reflect reality a bit more.
- wvenable 16y agoThe most frightening part of this debate is that people who are too lazy to properly define indexes are considering NoSQL solutions (and most of those require indexes too)! Properly utilizing a NoSQL requires more work than an RDMS, that's trade off for using a more low-level technology.