summaryrefslogtreecommitdiff
path: root/contrib/spi/moddatetime.c
diff options
context:
space:
mode:
authorBruce Momjian2007-02-01 19:10:30 +0000
committerBruce Momjian2007-02-01 19:10:30 +0000
commit8b4ff8b6a14096a28910fbff3d485f30dcb9a637 (patch)
treec250f17f4a8e3bfee442970a0666431ed8310650 /contrib/spi/moddatetime.c
parentbaaec74c5a953032049015883802660edd821cac (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/moddatetime.c')
-rw-r--r--contrib/spi/moddatetime.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/contrib/spi/moddatetime.c b/contrib/spi/moddatetime.c
index ca4e6c0f33..b4c9fe4de9 100644
--- a/contrib/spi/moddatetime.c
+++ b/contrib/spi/moddatetime.c
@@ -1,7 +1,7 @@
/*
moddatetime.c
-$PostgreSQL: pgsql/contrib/spi/moddatetime.c,v 1.13 2006/05/30 22:12:13 tgl Exp $
+$PostgreSQL: pgsql/contrib/spi/moddatetime.c,v 1.14 2007/02/01 19:10:23 momjian Exp $
What is this?
It is a function to be called from a trigger for the purpose of updating
@@ -43,7 +43,7 @@ moddatetime(PG_FUNCTION_ARGS)
if (TRIGGER_FIRED_FOR_STATEMENT(trigdata->tg_event))
/* internal error */
- elog(ERROR, "moddatetime: can't process STATEMENT events");
+ elog(ERROR, "moddatetime: cannot process STATEMENT events");
if (TRIGGER_FIRED_AFTER(trigdata->tg_event))
/* internal error */
@@ -56,7 +56,7 @@ moddatetime(PG_FUNCTION_ARGS)
rettuple = trigdata->tg_newtuple;
else
/* internal error */
- elog(ERROR, "moddatetime: can't process DELETE events");
+ elog(ERROR, "moddatetime: cannot process DELETE events");
rel = trigdata->tg_relation;
relname = SPI_getrelname(rel);