Re: INSERT ... ON CONFLICT IGNORE (and UPDATE) 3.0 - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: INSERT ... ON CONFLICT IGNORE (and UPDATE) 3.0
Date
Msg-id 553917AB.8030007@iki.fi
Whole thread Raw
In response to Re: INSERT ... ON CONFLICT IGNORE (and UPDATE) 3.0  (Peter Geoghegan <pg@heroku.com>)
Responses Re: INSERT ... ON CONFLICT IGNORE (and UPDATE) 3.0
List pgsql-hackers
On 04/20/2015 07:37 AM, Peter Geoghegan wrote:
>
>             if (wco->commandType == CMD_INSERT)
>                 command = "INSERT-applicable ";
>             else if (wco->commandType == CMD_UPDATE)
>                 command = "UPDATE-applicable ";
>             else if (wco->commandType == CMD_DELETE)
>                 command = "DELETE-applicable ";
>             else if (wco->commandType == CMD_SELECT)
>                 command = "SELECT-applicable ";
>
>             ereport(ERROR,
>                     (errcode(ERRCODE_WITH_CHECK_OPTION_VIOLATION),
>                  errmsg("new row violates %sWITH CHECK OPTION %sfor \"%s\"",
>                         command ? command : "",
>                         wco->secBarrier ? "(originally security barrier) ":"",
>                         wco->viewname),
>                     val_desc ? errdetail("Failing row contains %s.", val_desc) :
>                                0));

That code in ExecWithCheckOptions is not translatable. See style guide: 
http://www.postgresql.org/docs/devel/static/nls-programmer.html#NLS-GUIDELINES

- Heikki




pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: tablespaces inside $PGDATA considered harmful
Next
From: Petr Jelinek
Date:
Subject: Re: Freeze avoidance of very large table.