Tom Lane wrote on 22.11.2010 20:36:
I had the idea that the Windows version of psql was smart enough to
set client_encoding based on the console encoding it finds itself
running under, but I might be wrong about that. Or maybe you did
something that overrode its default?
I changed to "chcp 125
On 22 November 2010 19:36, Tom Lane wrote:
> I had the idea that the Windows version of psql was smart enough to
> set client_encoding based on the console encoding it finds itself
> running under, but I might be wrong about that. Or maybe you did
> something that overrode its default?
Apparentl
"Raymond O'Donnell" writes:
> On 22/11/2010 19:01, Thomas Kellerer wrote:
>> Tom Lane wrote on 22.11.2010 19:25:
>>> It looks to me like your console is not in fact producing UTF8;
>>> it's representing ö as 0xf6, which I think is right for Latin1.
>>> Select the proper client_encoding.
>> I assu
On 22/11/2010 19:01, Thomas Kellerer wrote:
Tom Lane wrote on 22.11.2010 19:25:
Thomas Kellerer writes:
I'm curious why the following is not working:
postgres=# show client_encoding;
client_encoding
-
UTF8
(1 row)
postgres=# create table umlaut_test_ö (id integer);
ERROR:
Tom Lane wrote on 22.11.2010 19:25:
Thomas Kellerer writes:
I'm curious why the following is not working:
postgres=# show client_encoding;
client_encoding
-
UTF8
(1 row)
postgres=# create table umlaut_test_ö (id integer);
ERROR: invalid byte sequence for encoding "
Thomas Kellerer writes:
> I'm curious why the following is not working:
> postgres=# show client_encoding;
> client_encoding
> -
> UTF8
> (1 row)
> postgres=# create table umlaut_test_ö (id integer);
> ERROR: invalid byte sequence for encoding "UTF8": 0xf6202869
It looks t
Hi,
I'm curious why the following is not working:
c:\psql postgres postgres
psql (9.0.1)
Type "help" for help.
postgres=# select version();
version
-
PostgreSQL 9.0.1, compiled by Visual C++ build 1500, 32-bi
