Committed by Greg Sabino Mullane <[email protected]> If you use something other than utf-8 for client encoding, you *will* need help. :)
--- Pg.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Pg.pm b/Pg.pm index b48108a..e01d61c 100644 --- a/Pg.pm +++ b/Pg.pm @@ -3795,7 +3795,7 @@ Not used by DBD::Pg. See the note about L</Cursors> elsewhere in this document. DBD::Pg has extensive support for a client_encoding of UTF-8, and most things like encoding and decoding should happen automatically. If you are -using a different encoding, you may need do the encoding and decoding +using a different encoding, you will need do the encoding and decoding yourself. For this reason, it is highly recommended to always use a client_encoding of UTF-8. The server_encoding can be anything, and no recommendations are made there, other than avoid SQL_ASCII whenever -- 1.8.4
