Re: [DBD::Pg] Another stab at the UTF-8 system, this time simplified as much as possible. See the pod for pg_enable_utf8 for an explanation. Note that this commit will probably be picked out later, as we want to release a new minor version before releasing such a big change

On Wed, Jul 03, 2013 at 01:26:19AM -0000, Greg Sabino Mullane wrote:
> David E. Wheeler wrote:
> > What happens if the client encoding is *not* UTF8? 
> 
> If not UTF8, we don't do anything. I think it is sufficient that we simply 
> require people to use UTF8 as their client_encoding if they want DBD::Pg 
> to do the right thing. It's very common, and more importantly, is the only 
> encoding guaranteed to auto convert from any server encoding.

For the record, there is no such guarantee, but MULE_INTERNAL is the only server
encoding presently lacking a conversion to UTF8.

-- 
Noah Misch
EnterpriseDB                                 http://www.enterprisedb.com