Re:A terrible schema from a clueless programmer
by mst on Sunday November 07, 2021 @01:30PM
(#29142056)
Multiple-long-column compound indices sucked in old mysqls if you could even convince it to use them in the first place.
Being able to look up each id via a single-string unique index would've almost certainly worked much better in those days.
Re:A terrible schema from a clueless programmer
by hn_throwaway_99 on Sunday November 07, 2021 @02:03PM
(#29142402)
I used MySql a lot back then, had many multi-column indexes, and never had an issue.
More importantly, given the degree of uniqueness likely to be present in many of those columns (like the email addresses), she could have gotten away with not indexing on every column.
Re:A terrible schema from a clueless programmer
by mst on Sunday November 07, 2021 @02:22PM
(#29142558)
Your first sentence was, I'm afraid, very much not a universal experience.
Your second is quite possibly true, but would have required experimentation to be sure of, and at some point "doing the thing that might be overkill but will definitely work" becomes a more effective use of developer time, especially when you have a groaning production system with live users involved.
The issue is that her analysis of what the issue was with her original table is completely wrong, and it's very weird given that the tone her "present" self is that it's so much more experienced and wise than her "inexperienced, naive" self.
My point is that she should give her inexperience self a break, all that was missing from her original implementation were some indexes.