[bearjaws]

IMO it also needs to default destructive statements (update, delete) to one row limit, and you have to explicitly choose to override that.

In the last 10 years of my career, many a dev & prod databases have been accidentally harmed by an overzealous query.

This could also add a warning for "left-over" non-updated rows, for example if the developer signals that only one row should be updated, but the WHERE clause has many rows, its usually a sign of a missing unique key, something I've seen before as well.