Re: BUG #6452: psql: can't change client encoding from the command line

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: BUG #6452: psql: can't change client encoding from the command line
Дата
Msg-id 4F3A566A.9060606@enterprisedb.com
обсуждение исходный текст
Ответ на BUG #6452: psql: can't change client encoding from the command line  (felix.gerzaguet@gmail.com)
Ответы Re: BUG #6452: psql: can't change client encoding from the command line  (Félix GERZAGUET <felix.gerzaguet@gmail.com>)
Список pgsql-bugs
On 11.02.2012 20:02, felix.gerzaguet@gmail.com wrote:
> Using the command line, I can't change the client encoding, but I can change
> it using the "\encoding" command :
>
> C:\>psql --variable=ENCODING=UTF8
> could not find a "psql" to execute
> could not find a "psql" to execute
> psql (9.1.2)
> WARNING: Console code page (850) differs from Windows code page (1252)
>           8-bit characters might not work correctly. See psql reference
>           page "Notes for Windows users" for details.
> Type "help" for help.
>
> postgres=# \encoding
> WIN1252
> postgres=# \echo :ENCODING
> WIN1252
> postgres=# \encoding UTF8
> postgres=# \encoding
> UTF8
> postgres=# \echo :ENCODING
> UTF8
> postgres=# \q

Yeah, "\set ENCODING UTF8" doesn't seem to work either. The "ENCODING"
psql variable tracks changes to the server's client_encoding setting,
but not vice versa. That probably should be fixed, or at least it should
throw an error telling the user to use \encoding instead.

As a workaround, you can set the PGCLIENTENCODING environment variable
before launching psql.

--
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

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

Предыдущее
От: tmpfs@hotmail.com
Дата:
Сообщение: BUG #6456: no password
Следующее
От: albert.cieszkowski@cc.com.pl
Дата:
Сообщение: BUG #6457: Regexp not processing word (with special characters on ends) correctly (UTF-8)