in reply to Re: Malformed UTF-8 character error after fetching data from Postgresql
in thread Malformed UTF-8 character error after fetching data from Postgresql
That is interesting, and I found another phrase in the DBD::Pg docs that sounds like I was mistaken:
pg_enable_utf8 (integer)
DBD::Pg specific attribute. The behavior of DBD::Pg with regards to this flag has changed as of version 3.0.0. ...
"Note that the value of client_encoding is only checked on connection time. If you change the client_encoding to/from 'UTF8' after connecting, you can set pg_enable_utf8 to -1 to force DBD::Pg to read in the new client_encoding and act accordingly."
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^3: Malformed UTF-8 character error after fetching data from Postgresql
by nihiliath (Initiate) on Jul 18, 2014 at 08:04 UTC | |
Re^3: Malformed UTF-8 character error after fetching data from Postgresql
by sundialsvc4 (Abbot) on Jul 17, 2014 at 22:08 UTC | |
by graff (Chancellor) on Jul 19, 2014 at 02:55 UTC |
In Section
Seekers of Perl Wisdom