Re: UTF-8 Encoding and Decoding (RT #40199)

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


> If the result is in text format, AND the value of client_encoding is
> 'UTF8', then the content is expected to be UTF8, REGARDLESS OF TYPE
> (yes, even for bytea, since it's escaped when you get it from the
> server). So the utf8 flag should be set in ALL such cases except when
> you've applied type-specific transformations to the result (such as in
> dequote_bytea).

...

> Assuming that DBD::Pg does, in fact, get back results in text format,
> it seems safe to assume that the text will always be in the format
> specified in client_encoding. If that's UTF-8, we could just set the
> utf8 flag on everything (except for bytea data). If we wanted to
> maximize backwards compatibility, we could do this only when
> pg_enable_utf8 is set to a true value, but it seems to me that it's
> not really necessary.
>
> So what would it take to make this change?

I dunno - does anyone else have opinions, pro or con? Sounds fairly
straightforward to me. I'd probably be in favor of just removing
pg_enable_utf8 entirely.

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

iEYEAREDAAYFAksq6egACgkQvJuQZxSWSsgKmACfddkmbPCVXCaxMY5fTONEhSKk
dJsAoMGtZCTfhyR7cymL280XX6UHAVwU
=I2E/
-----END PGP SIGNATURE-----