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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160



>> 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.

True, that. Thanks. We'll have to be careful how we word things.

- -- 
Greg Sabino Mullane greg-738XdyZ4GzZWk0Htik3J/[email protected]
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201307032220
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAlHU290ACgkQvJuQZxSWSsjHxACg3aDTtIVoweLP/BPV+f5a6STe
RWUAn2wVTVyXJdXRPlkSqxzylto3uxyk
=7L2F
-----END PGP SIGNATURE-----