-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
> Many thanks for the quick fix. Your welcome. > The way to check if the resulting string is still utf8-encoded (or, > rather, marked as such), is to test it with "Encode::is_utf8($string)". David applied those checks, thanks to you both for that. > I find that there is some ambiguity regarding the 'pg_enable_utf8' > attribute, and even wonder if it should be there at all. Yeah, I'm not sure either, but it may be due to the fact that we have to support Perl 5.6 as well. ...snip lots of good stuff... > I could see this as useful if one wanted to do some "bulk load" > or "bulk unload" of data to/from Pg, and knew in advance that no > translation is needed either way, to avoid the translation overhead. Yes, could be that too. > - to provide an easy call in DBD::Pg to get the internal database > encoding (with possibly a translation between the Pg encoding codes to > the corresponding Perl Encoding charset names) Yes, that should be easy enough. > - to provide explicit function calls to set the encoding layer to use > (or attributes to the connect()). Likewise. Thanks. I'm hesistant to do anything more than fix bugs at this point, but we definitely need to hash out the whole utf-8 business in a future release. - -- Greg Sabino Mullane [EMAIL PROTECTED] PGP Key: 0x14964AC8 200801221933 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFHlot6vJuQZxSWSsgRAyoAAKC/eSGMTOn8FDBkVBtSRNloZX71qQCggJdC ig9/pcozUZhPHoX26XMi2Wc= =veKq -----END PGP SIGNATURE-----
