Re: proposal: function parse_ident - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal: function parse_ident
Date
Msg-id CAFj8pRDugaRUcZg408gXT=iBgid2TBZ-aWYnm3XuYFTPw5DrAA@mail.gmail.com
Whole thread Raw
In response to Re: proposal: function parse_ident  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: proposal: function parse_ident  (Teodor Sigaev <teodor@sigaev.ru>)
List pgsql-hackers
Hi

2016-01-23 16:36 GMT+01:00 Tom Lane <tgl@sss.pgh.pa.us>:
Michael Paquier <michael.paquier@gmail.com> writes:
> On Sat, Jan 23, 2016 at 1:25 AM, Marko Tiikkaja <marko@joh.to> wrote:
> +                      errmsg("identifier contains disallowed chars"),
> +                      errdetail("string \"%s\" is not valid identifier",
> +                                     text_to_cstring(qualname))));
> Perhaps, "identifier contains not allowed character" is better?

"disallowed" reads better to me.  I agree with expanding "chars" to
"characters" though.  Also, the errdetail is conveying no actual extra
detail AFAICS.  I'd go with something like

        errmsg("identifier contains disallowed characters: \"%s\"",
               text_to_cstring(qualname)));

                        regards, tom lane




rebased, messages changes per Tom's proposal

Regards

Pavel
 





The errdeta

                        regards, tom lane




> --
> Michael


> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Victor Wagner
Date:
Subject: Re: Patch: Implement failover on libpq connect level.
Next
From: Thom Brown
Date:
Subject: Re: Patch: Implement failover on libpq connect level.