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

From Pavel Stehule
Subject Re: quoting psql varible as identifier
Date
Msg-id 162867790912291205l2e5b2cabm412756da49464e6e@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  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
2009/12/29 Tom Lane <tgl@sss.pgh.pa.us>:
> Pavel Stehule <pavel.stehule@gmail.com> writes:
>> 2009/12/29 Alvaro Herrera <alvherre@commandprompt.com>:
>>> Can we use a trick similar to pg_dump's?
>
>> I see it - we can move function (content) fmtId from dumputils.c to libpq.
>
> This is not a good idea.  pg_dump can be expected to be up-to-date with
> the backend's keyword list, but libpq cannot.
>
> Just quote the thing unconditionally.  It's not worth working harder
> than that anyway.

I see it.

Pavel

>
>                        regards, tom lane
>


pgsql-hackers by date:

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