Re: Escape handling in strings

From: AgentM <agentm(at)themactionfaction(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Escape handling in strings
Date: 2005-06-21 14:58:59
Message-ID: 82FD5DB6-B98C-4552-8091-E39CFFE009BE@themactionfaction.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

What I am really hoping for is that PQexecParams() [in later versions
of libpq] can figure it out for itself so client code doesn't need
fixing. That is the plan, right?

On Jun 20, 2005, at 11:57 PM, Oliver Jowett wrote:

> Bruce Momjian wrote:
>
>
>> I have received very few replies to my suggestion that we
>> implement E''
>> for escaped strings, so eventually, after a few major releases, we
>> can
>> have '' treat backslashes literally like the SQL standard requires.
>>
>
> Just checking: with this plan, a client needs to know what server
> version is in use to correctly escape strings, correct? That is, there
> is no escape mechanism that works correctly for both "old" and "new"
> servers?

|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-
AgentM
agentm(at)themactionfaction(dot)com
|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2005-06-21 15:23:38 Re: 8.03 postgres install error
Previous Message peter pilsl 2005-06-21 14:28:37 Re: renumber id's in correct order (compact id's)

Browse pgsql-hackers by date

  From Date Subject
Next Message MRB 2005-06-21 15:20:19 ENUM like data type
Previous Message Teodor Sigaev 2005-06-21 14:39:36 Re: GiST concurrency