freebsd-ports/databases/py-pyPgSQL/distinfo

SHA256 (pyPgSQL-2.5.1.tar.gz) = 498486f066f11a68f5b02a54ba5a008d01d507038c873bfd901c14d3f5ca18af
SIZE (pyPgSQL-2.5.1.tar.gz) = 152840
SHA256 (pyPgSQL-patch_byteaconn) = 73a324808aef49382e736245023eb8c468e1ca0803052a2a45162465b0ad28d7
SIZE (pyPgSQL-patch_byteaconn) = 4718
- Update to 2.5.1 Approved by: delphij (mentor, implicit) 2006-07-08 07:29:20 +02:00			`SHA256 (pyPgSQL-2.5.1.tar.gz) = 498486f066f11a68f5b02a54ba5a008d01d507038c873bfd901c14d3f5ca18af`
			`SIZE (pyPgSQL-2.5.1.tar.gz) = 152840`
PostgreSQL 8.3.1 has changed it's bytea encoding. * in PostgreSQL 8.3.1 Release note Make encode(bytea, 'escape') convert all high-bit-set byte values into \nnn octal escape sequences (Tom) This is necessary to avoid encoding problems when the database encoding is multi-byte. This change could pose compatibility issues for applications that are expecting specific results from encode. but pyPgSQL escape bytea encode as it's own implementments. PostgreSQL says that it may make failure(see PQescapeBytea documentation). in PQescapeBytea function documentation: "The only difference from PQescapeByteaConn is that PQescapeBytea does not take a PGconn parameter. Because of this, it cannot adjust its behavior depending on the connection properties (in particular, whether standard-conforming strings are enabled) and therefore it might give the wrong results. Also, it has no way to return an error message on failure." Patch is included upstream already PR: ports/122616 Submitted by: "Choe, Cheng-Dae" <whitekid@gmail.com> 2010-09-10 06:18:06 +02:00			`SHA256 (pyPgSQL-patch_byteaconn) = 73a324808aef49382e736245023eb8c468e1ca0803052a2a45162465b0ad28d7`
			`SIZE (pyPgSQL-patch_byteaconn) = 4718`