Mention "table" in "violates foreign key constraint" message that was

lacking it.  Perhaps it was suppressed because of line length
considerations, but "table" should appear.
This commit is contained in:
Bruce Momjian 2005-12-28 16:47:21 +00:00
parent a4e5169994
commit 776d63f975
1 changed files with 2 additions and 2 deletions

View File

@ -17,7 +17,7 @@
*
* Portions Copyright (c) 1996-2005, PostgreSQL Global Development Group
*
* $PostgreSQL: pgsql/src/backend/utils/adt/ri_triggers.c,v 1.83 2005/11/22 18:17:23 momjian Exp $
* $PostgreSQL: pgsql/src/backend/utils/adt/ri_triggers.c,v 1.84 2005/12/28 16:47:21 momjian Exp $
*
* ----------
*/
@ -3294,7 +3294,7 @@ ri_ReportViolation(RI_QueryKey *qkey, const char *constrname,
else
ereport(ERROR,
(errcode(ERRCODE_FOREIGN_KEY_VIOLATION),
errmsg("update or delete on \"%s\" violates foreign key constraint \"%s\" on \"%s\"",
errmsg("update or delete on table \"%s\" violates foreign key constraint \"%s\" on table \"%s\"",
RelationGetRelationName(pk_rel),
constrname, RelationGetRelationName(fk_rel)),
errdetail("Key (%s)=(%s) is still referenced from table \"%s\".",