Daniel Verite wrote:
> With DBD::Pg 3.5.3, the client output is:
> v3.5.3, sending é, getting back: é 2 4
> server log (log_statement=all), seen on a utf-8 terminal
> statement: SELECT 'é',length('é'),octet_length('é')
>
> My expectation was that 3.x would behave like 2.x with
> the above code, especially when pg_enable_utf8 is 0.
> It seems that with the newer version, it results
> in double encoding the parameter, as shown by
> the character and octet lengths at the server end.
It appears that my report is essentially the same as:
https://rt.cpan.org/Public/Bug/Display.html?id=103137
which also comes with a proposed bugfix, but it's been
left unprocessed so far.
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
