From 8b4ff8b6a14096a28910fbff3d485f30dcb9a637 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Thu, 1 Feb 2007 19:10:30 +0000 Subject: 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". --- src/backend/parser/parse_oper.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'src/backend/parser/parse_oper.c') diff --git a/src/backend/parser/parse_oper.c b/src/backend/parser/parse_oper.c index 55c40367218..c8d295047b3 100644 --- a/src/backend/parser/parse_oper.c +++ b/src/backend/parser/parse_oper.c @@ -8,7 +8,7 @@ * * * IDENTIFICATION - * $PostgreSQL: pgsql/src/backend/parser/parse_oper.c,v 1.93 2007/01/31 21:03:37 momjian Exp $ + * $PostgreSQL: pgsql/src/backend/parser/parse_oper.c,v 1.94 2007/02/01 19:10:27 momjian Exp $ * *------------------------------------------------------------------------- */ @@ -771,7 +771,7 @@ op_error(ParseState *pstate, List *op, char oprkind, errmsg("operator is not unique: %s", op_signature_string(op, oprkind, arg1, arg2)), errhint("Could not choose a best candidate operator. " - "You may need to add explicit type casts."), + "You might need to add explicit type casts."), parser_errposition(pstate, location))); else ereport(ERROR, @@ -779,7 +779,7 @@ op_error(ParseState *pstate, List *op, char oprkind, errmsg("operator does not exist: %s", op_signature_string(op, oprkind, arg1, arg2)), errhint("No operator matches the given name and argument type(s). " - "You may need to add explicit type casts."), + "You might need to add explicit type casts."), parser_errposition(pstate, location))); } -- cgit v1.2.3