Re: PQescapeByteaConn and the new hex encoding

From: Matteo Beccati <php(at)beccati(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PQescapeByteaConn and the new hex encoding
Date: 2009-12-25 18:17:43
Message-ID: 4B3501C7.4070901@beccati.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Il 25/12/2009 18:54, Tom Lane ha scritto:
> Matteo Beccati<php(at)beccati(dot)com> writes:
>> However, before taking a look at the actual code and understanding its
>> behaviour, I tried using "SET bytea_output = 'escape'" and I was
>> expecting PQescapeByteaConn to honour it.
>
> Why? PQescapeByteaConn's charter is to produce something that will work
> on the given connection, no more and no less.

Makes complete sense :)

I was just trying to find a way to get the PHP function pg_escape_bytea
(which uses PQescapeByteaConn if available) to generate a backwards
compatible escaped string. It's probably just a corner case though and
it can be dealt with at the client side, if necessary.

Cheers
--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2009-12-25 18:29:50 proposal for 8.5, listagg aggregate function, WIP patch
Previous Message Pavel Stehule 2009-12-25 18:03:05 Re: info about patch: using parametrised query in psql