Andy Levy has a new reason for us:
I got a merge a while back that included a change I wasn’t expecting from one of my developers. All they were doing was renaming a column on a table. We had names settled a while ago. What’s up with that?
Turns out, when I created the table, I named one of the fields
BrithYear
. This merge request corrected it toBirthYear
. The misspelling slipped past me, past everyone else, it was only discovered because when this developer was building the a new query into their code, they spelled the field as one would expect, and the query threw an error.
There’s many a reason not to use SELECT *
in application code; this is one I don’t think I’d heard before.