Author here. I agree with you that training engineers on SQL would be a great action item coming from a postmortem. I was trying to emphasize resisting shutting off access as "the fix" for the problem. We don't want to blame engineers for not having the knowledge - we want to level up their skills if that contributed to the issue. I think you're asking the right kinds of questions.
"Why didn't [Engineer X] know enough SQL to understand that query would break the database?"
being bad (While "We need to shut off his/her access." is).
Post mortems have many different levels, technology -> people -> processes -> org -> culture. It's not wrong talking about people, it's wrong to blame them though and stop with people. Asking 'Why?' only stops with company culture.
Usually people make mistakes, they don't want to break things. It doesn't help to not talk about people, but it's important to ask why the person in question acted the way (s)he did. Would others do the same? (most probably) Why? UI issues? Documentation issues? Too many concurrent warnings? etc.
Also important to look from the situation forward (incident happening), not from now backwards (hindsight).
To the SQL question one could ask about the training, reviews, ...