Skip site navigation (1) Skip section navigation (2)

Re: problem connecting via ODBC when unicode (now in correct forum.).

From: Kim Mortensen <kimfmx(at)gmail(dot)com>
To: Hiroshi Saito <hiroshi(at)winpg(dot)jp>
Cc: adrian(dot)klaver(at)gmail(dot)com, pgsql-odbc(at)postgresql(dot)org
Subject: Re: problem connecting via ODBC when unicode (now in correct forum.).
Date: 2011-01-21 18:20:41
Message-ID: AANLkTimYsGV2cVmtY7JBgh1yrR2N2HW+NryEBa4MhB78@mail.gmail.com (view raw or flat)
Thread:
Lists: 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

2011/1/21 Hiroshi Saito <hiroshi(at)winpg(dot)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 "זרו"
>>
>
>

In response to

Responses

pgsql-odbc by date

Next:From: Adrian KlaverDate: 2011-01-21 20:28:26
Subject: Re: problem connecting via ODBC when unicode (now in correct forum.).
Previous:From: Hiroshi SaitoDate: 2011-01-21 18:16:34
Subject: Re: problem connecting via ODBC when unicode (now in correct forum.).

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group