Re: BUG #6246: character encoding for 64 bit

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: BUG #6246: character encoding for 64 bit
Дата
Msg-id 4E9577B30200002500041EB4@gw.wicourts.gov
обсуждение исходный текст
Ответ на Re: BUG #6246: character encoding for 64 bit  (Susannah <cyclingrelf@gmail.com>)
Ответы Re: BUG #6246: character encoding for 64 bit  (bushcraftrelf <cyclingrelf@gmail.com>)
Список pgsql-bugs
Дерево обсуждения 
Susannah <cyclingrelf@gmail.com> wrote:

> FATAL:  conversion between WIN1252 and LATIN1 is not supported

WIN1512 supports characters which are not supported by LATIN1.  If
you sent such characters to the database, what would you expect to
happen?

> I can connect through pgAdmin and create tables etc, just not with
> psql.

Perhaps pgAdmin detects the mismatch and sets the client-side
character set to the more limited LATIN1?  What does pgAdmin do if
you make such a connection and then try to store a character which
is not in the LATIN1 character set, like a euro character?

-Kevin

В списке pgsql-bugs по дате отправления:

Предыдущее
От: "Laurian Vostinar"
Дата:
Сообщение: BUG #6253: JDBC driver: getIndexInfo() returns quotes around quoted column names
Следующее
От: "Kevin Grittner"
Дата:
Сообщение: Re: BUG #6252: After drop the default database 'postgres', I can not create a database by 'createdb.exe'