-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
> Well, it doesn't work for me, at least not for error messages > resulting from DBI->connect(). Ah, yes, that's unfortunately true - it's too early for the code to have already parsed and internalized the attribute hash inside the connect call. It's possible we could set enable_utf8 to an indeterminate state and default to UTF-8 if we are in that state. I'm grumpily tempted to just flip it on for all cases :) but we should probably just clean up all of the UTF-8 stuff at once be removing the main function of pg_enable_utf8 (while keeping it for backwards compat, as mentioned in another thread). - -- Greg Sabino Mullane [email protected] PGP Key: 0x14964AC8 201001211153 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAktYhqAACgkQvJuQZxSWSsgg1wCfY2P+PmCtc8HMweorOyLZczUO oGEAoPVImqJrMmR1uJtXeKuTQRNJ3yFC =CX8T -----END PGP SIGNATURE-----
