Re: problem connecting via ODBC when unicode (now in correct forum.).
От | Kim Mortensen |
---|---|
Тема | Re: problem connecting via ODBC when unicode (now in correct forum.). |
Дата | |
Msg-id | AANLkTimYsGV2cVmtY7JBgh1yrR2N2HW+NryEBa4MhB78@mail.gmail.com обсуждение исходный текст |
Ответ на | problem connecting via ODBC when unicode (now in correct forum.). (Kim Mortensen <kimfmx@gmail.com>) |
Ответы |
Re: problem connecting via ODBC when unicode (now in correct
forum.).
|
Список | pgsql-odbc |
Thank you for your input,
it may be that only ascii chars is to be used, however it should be stated or a bug report filled out, as you can insert Login Roles with different charakterset as you can actually use.
Best Regards
Kim Mortesnen
it may be that only ascii chars is to be used, however it should be stated or a bug report filled out, as you can insert Login Roles with different charakterset as you can actually use.
Best Regards
Kim Mortesnen
2011/1/21 Hiroshi Saito <hiroshi@winpg.jp>
Hi.
I think..
your create role "זרו" was saved by pgAdmin by UTF-8 in the database.
pgAdmin uses the input value of connection directly, however, input value is in coincidence by UTF-8. however, psqlODBC uses the character code of environmental dependence as it is.
as for japanese windows, It is not in agreement with a database by the reason for being SJIS. In the client-server protocol of PostgrSQL, judgment of encoding can't be performed at the time of connection.
therefore, I think that it is difficult to support. however, It may be useful to evasion of a security risk that it uses understanding this specification. but, handling is not recommendation in the reason for being difficult. Probably, only the ASCII character should be used.
I may have misunderstanding.?
Regards,
Hiroshi Saito
(z-saito@ address was lost...)
(2011/01/22 1:48), Kim Mortensen wrote:create role "זרו"
В списке pgsql-odbc по дате отправления: