Matteo Beccati wrote:
Il 25/12/2009 18:54, Tom Lane ha scritto:
Matteo Beccati<p...@beccati.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.
There is plenty of reason to use hex format wherever possible - we
expect it to be much more efficient to process on the server side.
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
