Message-ID: <020201c3a7f7$1b218c50$1f324d80@w2k>
From: "Hiroshi Saito" <saito@inetrt.skcapi.co.jp>
To: "Andreas Pflug" <pgadmin@pse-consulting.de>,
	"=?Windows-1251?B?xOzo8vDo6SDP7u/u4g==?=" <ibmpc@mail.ru>
Cc: <pgadmin-support@postgresql.org>
References: <947980921.20031110115514@mail.ru>
	<3FB02583.7070203@pse-consulting.de>
Subject: Re: Bug
Date: Tue, 11 Nov 2003 10:57:04 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1251"
Content-Transfer-Encoding: 8bit

Dear Дмитрий Попов .

I believe the reappearance of this problem.
IMHO,You must not use multi-byte for the user ID.

It seems you that it that a user was made under the condition of the multi-byte
connection is right by the intervention of conversion.
However,
The user character line won't correspond so far as conversion is never minded
at the time of the connection connection.

regards,
Hiroshi Saito

----- Original Message -----
From: "Andreas Pflug" <pgadmin@pse-consulting.de>
To: "Дмитрий Попов" <ibmpc@mail.ru>
Cc: <pgadmin-support@postgresql.org>
Sent: Tuesday, November 11, 2003 8:55 AM
Subject: Re: [pgadmin-support] Bug


> Дмитрий Попов wrote:
>
> >pgAdmin III, v1.0.0, pgSql 7.3.1 Windows Russian
> >
> >Hello!
> >
> >PostrgeSQL on windows make SuperUser's name symbols as current system
> >user. When user in windows include russian, PgSQL make user with
> >russian symbols too.
> >But pgAmin replace it to "_".
> >
> >
> >For Example: My user was "Dmitriy" (Дмитрий). There is PgSQL error:
> >'Uncknown user "_______"'.
> >
> >I know, that russian usernames it's bad, but differnt other pgSQL
> >manager's (like EMS PostrgeSQL manager) work with russian names
> >correct.
> >
> >
> >
> >
> >
> Hi Dmitriy,
>
> actually I didn't understand exactly what the problem is, so I'm
> guessing that you got a conversion problem. Do you have SQL_ASCII as
> database encoding? If yes, this is a problem, because Russian characters
> are not ascii.
> There are two options:
>
> 1) (the better option)
> use UNICODE or the Russian encoding in the database.
>
> 2) Use a newer pgAdmin3 version, we have a new workaround for SQL_ASCII
> databases with wrong characters.
>
> Regards,
> Andreas
>
> >P.S. Sorry for my English - i'm from Russia and speak English very
> >bad.
> >