Re: quoting psql varible as identifier

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: quoting psql varible as identifier
Date: 2010-01-21 15:00:36
Message-ID: 603c8f071001210700g20f66641oc4e19087ac1c061f@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 19, 2010 at 11:19 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Jan 19, 2010 at 4:40 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>>> I'd like to proceed by committing an initial patch which changes the
>>> "Escaping Strings for Inclusion in SQL Commands" to use a
>>> <variablelist> with one <varlistentry> per function (as we do in
>>> surrounding functions) and consolidates it with the following section,
>>>  "Escaping Binary Strings for Inclusion in SQL Commands".  Then I'll
>>> submit a patch implementing pqEscapeLiteral() and pqEscapeIdentifier()
>>> as discussed here, and the doc diff hunks will actually be readable.
>>
>> Sounds like a plan.
>
> Initial commit done, and follow-on patch attached.  The docs took
> longer to write than the code.  I spent a fair amount of time trying
> to make it all make sense, but suggestions are welcome.

Committed after fixing a couple of oversights in my doc changes.

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-01-21 15:07:23 Re: lock_timeout GUC patch
Previous Message Tom Lane 2010-01-21 14:54:47 Re: Git out of sync vs. CVS