diff options
| author | Bruce Momjian <bruce@momjian.us> | 2007-02-01 19:10:30 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2007-02-01 19:10:30 +0000 |
| commit | 8b4ff8b6a14096a28910fbff3d485f30dcb9a637 (patch) | |
| tree | c250f17f4a8e3bfee442970a0666431ed8310650 /contrib/spi/refint.c | |
| parent | baaec74c5a953032049015883802660edd821cac (diff) | |
Wording cleanup for error messages. Also change can't -> cannot.
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
Diffstat (limited to 'contrib/spi/refint.c')
| -rw-r--r-- | contrib/spi/refint.c | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/contrib/spi/refint.c b/contrib/spi/refint.c index 17735fca845..c0c55eb080e 100644 --- a/contrib/spi/refint.c +++ b/contrib/spi/refint.c @@ -77,7 +77,7 @@ check_primary_key(PG_FUNCTION_ARGS) /* Should be called for ROW trigger */ if (TRIGGER_FIRED_FOR_STATEMENT(trigdata->tg_event)) /* internal error */ - elog(ERROR, "check_primary_key: can't process STATEMENT events"); + elog(ERROR, "check_primary_key: cannot process STATEMENT events"); /* If INSERTion then must check Tuple to being inserted */ if (TRIGGER_FIRED_BY_INSERT(trigdata->tg_event)) @@ -86,7 +86,7 @@ check_primary_key(PG_FUNCTION_ARGS) /* Not should be called for DELETE */ else if (TRIGGER_FIRED_BY_DELETE(trigdata->tg_event)) /* internal error */ - elog(ERROR, "check_primary_key: can't process DELETE events"); + elog(ERROR, "check_primary_key: cannot process DELETE events"); /* If UPDATion the must check new Tuple, not old one */ else @@ -277,12 +277,12 @@ check_foreign_key(PG_FUNCTION_ARGS) /* Should be called for ROW trigger */ if (TRIGGER_FIRED_FOR_STATEMENT(trigdata->tg_event)) /* internal error */ - elog(ERROR, "check_foreign_key: can't process STATEMENT events"); + elog(ERROR, "check_foreign_key: cannot process STATEMENT events"); /* Not should be called for INSERT */ if (TRIGGER_FIRED_BY_INSERT(trigdata->tg_event)) /* internal error */ - elog(ERROR, "check_foreign_key: can't process INSERT events"); + elog(ERROR, "check_foreign_key: cannot process INSERT events"); /* Have to check tg_trigtuple - tuple being deleted */ trigtuple = trigdata->tg_trigtuple; |