Now that I think of it, pg_escape_bytea operates on a handle to the
current database connection, and I believe it queries the value of
standard_conforming_strings so that it can determine how the data should
be escaped. I think I verified this by testing some time ago, although
I hadn't thought of it until just now, and I would need to test again to
make sure.
Sorry I didn't think this through more carefully before I wrote.
Thanks
Lewis
Kevin Grittner wrote:
Lewis Kapell <lkapell@xxxxxxxxxxxxx> wrote:
I forgot to mention that all of these insertions are being done
via PHP scripts, and we are using the pg_escape_bytea function
(part of the PHP Postgres extension) to escape the data being
inserted into bytea columns. Rather important item, that.
Does this address all the concerns which you raised?
I'm not familiar with that extension or its functions, but it sounds
like you're probably in better shape than I thought when I read your
first email. :-)
Perhaps someone who knows that extension can comment on the issues
around E'' literals, the escape_string_warning setting and the
standard_conforming_strings setting.
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
