Clarify to the translator that plpgsql_yyerror() deals with the translation
of "syntax error", not the literal string. This same change was made in the backend a while ago; but it applies to plpgsql as well.
This commit is contained in:
parent
15a3fe6d63
commit
125a5b95d8
|
@ -9,7 +9,7 @@
|
||||||
*
|
*
|
||||||
*
|
*
|
||||||
* IDENTIFICATION
|
* IDENTIFICATION
|
||||||
* $PostgreSQL: pgsql/src/pl/plpgsql/src/scan.l,v 1.69 2009/04/19 21:50:09 tgl Exp $
|
* $PostgreSQL: pgsql/src/pl/plpgsql/src/scan.l,v 1.70 2009/06/10 22:34:11 petere Exp $
|
||||||
*
|
*
|
||||||
*-------------------------------------------------------------------------
|
*-------------------------------------------------------------------------
|
||||||
*/
|
*/
|
||||||
|
@ -441,7 +441,7 @@ plpgsql_yyerror(const char *message)
|
||||||
{
|
{
|
||||||
ereport(ERROR,
|
ereport(ERROR,
|
||||||
(errcode(ERRCODE_SYNTAX_ERROR),
|
(errcode(ERRCODE_SYNTAX_ERROR),
|
||||||
/* translator: %s is typically "syntax error" */
|
/* translator: %s is typically the translation of "syntax error" */
|
||||||
errmsg("%s at end of input", _(message)),
|
errmsg("%s at end of input", _(message)),
|
||||||
internalerrposition(cursorpos),
|
internalerrposition(cursorpos),
|
||||||
internalerrquery(scanstr)));
|
internalerrquery(scanstr)));
|
||||||
|
@ -450,7 +450,7 @@ plpgsql_yyerror(const char *message)
|
||||||
{
|
{
|
||||||
ereport(ERROR,
|
ereport(ERROR,
|
||||||
(errcode(ERRCODE_SYNTAX_ERROR),
|
(errcode(ERRCODE_SYNTAX_ERROR),
|
||||||
/* translator: first %s is typically "syntax error" */
|
/* translator: first %s is typically the translation of "syntax error" */
|
||||||
errmsg("%s at or near \"%s\"", _(message), loc),
|
errmsg("%s at or near \"%s\"", _(message), loc),
|
||||||
internalerrposition(cursorpos),
|
internalerrposition(cursorpos),
|
||||||
internalerrquery(scanstr)));
|
internalerrquery(scanstr)));
|
||||||
|
|
Loading…
Reference in New Issue