On Wed, Nov 25, 2009 at 15:41, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Magnus Hagander <magnus@hagander.net> writes:
>> FWIW, this patch also *completely* breaks the default windows
>> installs, which will have the database in UTF-8 but there is *never*
>> any UTF-8 support on the console (only UTF-16).
>
> Hmm ... so how do we work with utf-8 data in the database? That
> should be the same case AFAICS.
It breaks, yes :-), and you have to set the client encoding manually.
But it works in the simple case where your data is ASCII for example.
Which usually means it's fine for listing databases, or database
objects, or such things. But with the unicode line patch, it's
basically completely useless, not just partially annoying.
-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/