Re: client encoding SQL_ASCII for server SQL_ASCII - Mailing list pgadmin-hackers

From Hiroshi Saito
Subject Re: client encoding SQL_ASCII for server SQL_ASCII
Date
Msg-id 01ac01c3883a$c9173d50$1f324d80@w2k
Whole thread Raw
In response to client encoding SQL_ASCII for server SQL_ASCII  ("Dave Page" <dpage@vale-housing.co.uk>)
List pgadmin-hackers
There is no error in every place.
But, there is one place of the problem.
It is a quote problem by the renewal of data view.

regards,
Hiroshi Saito

----- Original Message -----
From: "Hiroshi Saito" <saito@inetrt.skcapi.co.jp>

> Hmm..
>
> From: "Andreas Pflug" <pgadmin@pse-consulting.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


pgadmin-hackers by date:

Previous
From: "Serguei A. Mokhov"
Date:
Subject: Re:
Next
From: "Hiroshi Saito"
Date:
Subject: Re: client encoding SQL_ASCII for server SQL_ASCII