Skip site navigation (1) Skip section navigation (2)

Re: quoting psql varible as identifier

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: quoting psql varible as identifier
Date: 2009-12-29 19:50:40
Message-ID: 162867790912291150o724a0b81p6f07b64602fc7b96@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
2009/12/29 Alvaro Herrera <alvherre(at)commandprompt(dot)com>:
> Pavel Stehule escribió:
>> 2009/12/29 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> > Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>> >> so we cannot simply implement quote_ident on client side :(. So we
>> >> have to use a real query.
>> >
>> >> It is acceptable for you?
>> >
>> > No, certainly not --- that adds a boatload of failure conditions.
>> > Just quote it unconditionally.
>>
>> ok
>>
>> this function have to live in libpq - it needs some not exported
>> functionality. But, it would not be a problem.
>
> Can we use a trick similar to pg_dump's?
>

I see it - we can move function (content) fmtId from dumputils.c to libpq.

Pavel

> --
> Alvaro Herrera                                http://www.CommandPrompt.com/
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2009-12-29 19:52:18
Subject: Re: quoting psql varible as identifier
Previous:From: Pavel StehuleDate: 2009-12-29 19:47:20
Subject: Re: quoting psql varible as identifier

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group