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

From Robert Haas
Subject Re: quoting psql varible as identifier
Date
Msg-id 603c8f071001191046o6e63189cv9ec08941e0c8a5cd@mail.gmail.com
Whole thread Raw
In response to Re: quoting psql varible as identifier  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: quoting psql varible as identifier  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: quoting psql varible as identifier  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Tue, Jan 19, 2010 at 1:43 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> Updated patch attached.  I still think this is a bizarre API.
>
> Well, if we had it to do over I'm sure we'd have done it differently,
> but the functions are there now and we aren't going to change them ...

I agree, but I don't feel the need to repeat the mistakes we've
already made by slavishly copying them into new places.  I think as
long as we're adding a new function, we should make it behave sanely.
We could even take the opportunity to go back and add a saner version
of PQescapeStringConn.

...Robert


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: quoting psql varible as identifier
Next
From: Tom Lane
Date:
Subject: Re: quoting psql varible as identifier