Re: client encoding SQL_ASCII for server SQL_ASCII

From: "Hiroshi Saito" <saito(at)inetrt(dot)skcapi(dot)co(dot)jp>
To: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>, "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
Cc: "pgadmin-hackers" <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: client encoding SQL_ASCII for server SQL_ASCII
Date: 2003-10-01 15:54:49
Message-ID: 017201c38834$584a7f20$1f324d80@w2k
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hmm..

From: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>

> Dave Page wrote:
>
> >Should that be back patched for 1.0.1? Seems like a bug to me.
> >
> >
> >
>
> The bug is the non-ascii data...
> Yes, we should back-patch that. Just plain pgConn.cpp and pgConn.hpp.
>
> Regards,
> Andreas

Please wait a little.
Is this taken into consideration?

saito=# \l
List of databases
Name | Owner | Encoding
------------+-------+-----------
pgdata | saito | UNICODE
regression | saito | EUC_JP
saito | saito | EUC_JP
template0 | saito | EUC_JP
template1 | saito | EUC_JP
with | saito | SQL_ASCII
(6 rows)

Regards,
Hiroshi Saito

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Serguei A. Mokhov 2003-10-01 15:57:30 Re:
Previous Message Dave Page 2003-10-01 15:44:44 Re: utffile.cpp & expatd.lib