Hi! > On Fri, Jul 28, 2017 at 06:52:44PM +0200, Christoph Zwerschke > <[email protected]> wrote: > Am 26.07.2017 um 23:49 schrieb Oleg Broytman: > > Shouldn't unescape_bytea(escape_bytea()) be idempotent? > > See https://www.postgresql.org/docs/9.6/static/libpq-exec.html > > "PQunescapeBytea is not exactly the inverse of PQescapeBytea, because the > string is not expected to be "escaped" when received from PQgetvalue. In > particular this means there is no need for string quoting considerations, > and so no need for a PGconn parameter."
I see. Thank you! I use now a slightly different encoding, initially created for py-postgresql driver, compatible with unescape_bytea. https://github.com/sqlobject/sqlobject/commit/48e108f21e03c907b704220726631c0347e05df0 All my tests for PyGreSQL now passed: https://travis-ci.org/sqlobject/sqlobject/builds/259124048 > -- Chris Oleg. -- Oleg Broytman http://phdru.name/ [email protected] Programmers don't die, they just GOSUB without RETURN. _______________________________________________ PyGreSQL mailing list [email protected] https://mail.vex.net/mailman/listinfo.cgi/pygresql
