Re: BUG #6510: A simple prompt is displayed using wrong charset

Поиск
Список
Период
Сортировка
От Alexander LAW
Тема Re: BUG #6510: A simple prompt is displayed using wrong charset
Дата
Msg-id 4F68DF76.1030609@gmail.com
обсуждение исходный текст
Ответ на Re: BUG #6510: A simple prompt is displayed using wrong charset  (Alvaro Herrera <alvherre@commandprompt.com>)
Ответы Re: BUG #6510: A simple prompt is displayed using wrong charset  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: BUG #6510: A simple prompt is displayed using wrong charset  (Noah Misch <noah@leadboat.com>)
Список pgsql-bugs
Thanks, I've understood your point.
Please look at the patch. It implements the first way and it makes psql
work too.

Regards,
Alexander

20.03.2012 00:05, Alvaro Herrera пишет:
> Excerpts from Alexander LAW's message of dom mar 18 06:04:51 -0300 2012:
>> I see two ways to resolve the issue.
>> First is to use CharToOemBuff when writing a string to the "con" and
>> OemToCharBuff when reading an input from it.
>> The other is to always use stderr/stdin for Win32 as it was done for
>> msys before. I think it's more straightforward.
> Using console directly instead of stdin/out/err is more appropriate when
> asking for passwords and reading them back, because you can redirect the
> rest of the output to/from files or pipes, without the prompt
> interfering with that.  This also explains why stderr is used instead of
> stdout.
>


Вложения

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

Предыдущее
От: Merlin Moncure
Дата:
Сообщение: Re: [GENERAL] Altering a table with a rowtype column
Следующее
От: neeraj.punmiya@securetogether.com
Дата:
Сообщение: BUG #6548: NOWAIT does not work in Select statement if table is locked using "Lock " command