Change PostgreSQL backend to use PQescapeStringConn
authorJonathan McDowell <noodles@earth.li>
Sat, 26 Dec 2009 12:16:02 +0000 (12:16 +0000)
committerJonathan McDowell <noodles@earth.li>
Sat, 26 Dec 2009 12:16:02 +0000 (12:16 +0000)
  While the PostgreSQL backend is not known to be in use anywhere we were
  using an older escaping function (PQescapeString) which does not have
  knowledge of the connection character encoding and so has potential
  problems. Switch to using PQescapeStringConn, which does have this
  knowledge.


No differences found