mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Clarify to the translator that plpgsql_yyerror() deals with the translation

Browse Source 
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:
Peter Eisentraut 2009-06-10 22:34:11 +00:00
parent 15a3fe6d63
commit 125a5b95d8
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/pl/plpgsql/src/scan.l
View File

@ -9,7 +9,7 @@
*
*
* 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,
(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)),
internalerrposition(cursorpos),
internalerrquery(scanstr)));
@ -450,7 +450,7 @@ plpgsql_yyerror(const char *message)
{
ereport(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),
internalerrposition(cursorpos),
internalerrquery(scanstr)));