-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
> p5-DBD-Pg-1.49 Ah, there's the problem. That's a very old version of DBD::Pg (from May 2006). Many bugs have been fixed since that version, incluing some UTF8-related ones. Your script worked fine for me here on a Linux box running DBD::Pg 2.11.5. It's possible but unlikely that something else in your stack is causing the problem, so your best bet is to try a modern version of DBD::Pg. For what's it worth, here's what my script printed. (Take with a grain of salt, it will probably get munged somewhere from my screen to yours, but it looked good): 10 ABCDE: UTF8 off, ASCII, 5 characters 5 bytes 20 : UTF8 off, non-ASCII, 10 characters 10 bytes 30 russian russian: UTF8 off, non-ASCII, 26 characters 26 bytes 40 russian russian: UTF8 off, non-ASCII, 42 characters 42 bytes > postgresql-client-8.2.6 Postgres is up to 8.2.13, you should strongly consider upgrading this as well. It's a simple binary upgrade, no data reload needed. - -- Greg Sabino Mullane [email protected] End Point Corporation PGP Key: 0x14964AC8 200903152307 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkm9wrwACgkQvJuQZxSWSsjGSgCg3lFfxRaV7t4Ly6POm1VLslHO 2soAn2qbVrfgqlEgwa3ltXqRiyb8Ovvu =GGJ7 -----END PGP SIGNATURE-----
