3 ms·
That's exactly what I thought. I consulted on an enterprise project once with EVERY column in EVERY table set to string because the engineers didn't want to th
by odammit 9y ago
That's exactly what I thought.
I consulted on an enterprise project once with EVERY column in EVERY table set to string because the engineers didn't want to think about datatypes.
All the queries used wild cards or just pulled back a ton of data and did the filtering and sorting in the application code.
That job sucked.
- mkempe 9y agoI consulted on a large healthcare data project with similar problems. Even "primary" keys were strings. Most tables had no indexes. (The developers routinely argued that they needed new servers with more RAM because they couldn't run multiple database queries at the same time. They already had 64 GB RAM.)
- odammit 9y agoYes! It had a lot of index-less tables. The you put an index on something and everyone treats you like a magician after you convince them the additional write is worth it.
- mkempe 9y agoOr one of the developers deletes the index you've just added... because it uses too much disk space.
- rlonstein 9y agoNo, no, no! They get religion and put an index on every column.
- fujiters 9y agoMost days I worry I'm an imposter, but when I hear that there are groups of people running databases with no idea that indexes are a thing, I think maybe I should ask for a raise.