What sort of baffles me is deploying a database change, but not the application code that's linked to those changes. Why would you want to do that? Can't remember having ever done something like that, app + DB = system, always.
Second thing is, not having a script in place to quickly roll back those changes. Mistakes are human but you should always have a "plan B" or a recovery plan in place.
"SELECT *" might not be really recommended as a 'best practice' but I don't see it as the root cause of the fiasco. The root cause is more "tunnel vision" (focusing on one aspect only and overlooking other ones).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
What sort of baffles me is deploying a database change, but not the application code that's linked to those changes. Why would you want to do that? Can't remember having ever done something like that, app + DB = system, always.
Second thing is, not having a script in place to quickly roll back those changes. Mistakes are human but you should always have a "plan B" or a recovery plan in place.
"SELECT *" might not be really recommended as a 'best practice' but I don't see it as the root cause of the fiasco. The root cause is more "tunnel vision" (focusing on one aspect only and overlooking other ones).