Re: Naming conventions for special database objects

>> Aren't you assuming that all DBMS vendors will provide adequate PK/FK
info
(without the constraint name) when an error occurs? <<

Yes; the table name and the PRIMARY KEY violation should be in the
exception message and SQLSTATE code.

>> There could be multiple FK columns on a table which reference the same
PK table (e.g., a PK  table of valid states or countries). <<

But each of the FK columns will have a different column name which
shows the role being played by the data element, which should be in
the error message and SQLSTATE code.  If I reference Personnel(emp_id)
twice in a table4, then one of them might "mgr_emp_id" and
"assistant_emp_id"  -- the role each one plays shown in their prefix.