Re: quoting psql varible as identifier - Mailing list pgsql-hackers

From Robert Haas
Subject Re: quoting psql varible as identifier
Date
Msg-id 603c8f071001141746l414b519fg6e22c32dae2e0c1a@mail.gmail.com
Whole thread Raw
In response to Re: quoting psql varible as identifier  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: quoting psql varible as identifier
Re: quoting psql varible as identifier
List pgsql-hackers
On Mon, Jan 11, 2010 at 6:54 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
>> No longer applies, please rebase.
>
> fixed, sorry

Hmm.  I think that pqEscapeIdentConn should be in a separate section
of the documentation, entitled "Escaping Identifiers for Inclusion in
SQL Commands".  Or else we should merge the existing sections
"Escaping Strings for Inclusion in SQL Commands" and "Escaping Binary
Strings for Inclusion in SQL Commands" and then put this in there too.

On a perhaps-related note, does anyone understand why "Escaping
Strings for Inclusion in SQL Commands" is formatted in a way that is
needlessly inconsistent with the preceding and following sections?  I
was surprised by the magnitude of the doc diff hunk in this patch, but
when I looked at it it seems to read more clearly with these changes.

I have yet to fully review the code but on a quick glance it looks reasonable.

...Robert


pgsql-hackers by date:

Previous
From: KaiGai Kohei
Date:
Subject: Re: [PATCH] remove redundant ownership checks
Next
From: Robert Haas
Date:
Subject: Re: KNNGiST for knn-search (WIP)