PQescapeByteaConn and the new hex encoding

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

Hi everyone,

I've been playing with the 8.5alpha3 in the last few days. Among other
things, I'm making sure that the pgsql PHP extensions still work
correctly with the new version. It would seems so, as all the errors in
the standard pgsql extension test suite come from the fact that
PQescapeByteaConn now defaults to the new "hex" format when connected to
a 8.5+ server, which is cool. It's just a matter of updating the tests.

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. Not sure if changing the
current behaviour is at all possible, desirable and really worth it, but
I'm going to hold the patches to the php test suite until I get some
feedback here.

Thoughts?

Cheers
--
Matteo Beccati

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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-12-25 17:26:44 Re: info about patch: using parametrised query in psql
Previous Message Bruce Momjian 2009-12-25 15:12:35 Re: Removing pg_migrator limitations