It's just an example. There are several things that can go wrong during database insertion or update, some of which depend on user input, so need to be registered as a form error.

In those cases the you'd get a list of catches, plus a catch-all that would just dump the actual error message

It would probably need a change right down at the DBD/DBI level, and the way the drivers register their error handlers

--
Lyon