Re: BUG #4890: Allow insert character has no equivalent in "LATIN2" - Mailing list pgsql-bugs

From Craig Ringer
Subject Re: BUG #4890: Allow insert character has no equivalent in "LATIN2"
Date
Msg-id 1246273489.11346.11.camel@ayaki
Whole thread Raw
In response to BUG #4890: Allow insert character has no equivalent in "LATIN2"  ("saint" <saint@akpa.pl>)
List pgsql-bugs
On Sat, 2009-06-27 at 19:20 +0000, saint wrote:

> set client_encoding to 'WIN1250';
> insert into public.test(col) values('‰');

You're lying to the server about the client encoding in one or both
cases. I can't know which without knowing what program you're talking to
the server with and how it's set up.

'SET client_encoding' tells the server what encoding to expect incoming
data in. It doesn't change what encoding the client sends that data in.
If your client has a different default encoding to that of the server,
you can inform the server that the client will be sending differently
encoded data.

In other words, you can't use 'SET client_encoding' to change what
encoding the client uses, only how the server interprets the bytes it
gets from the client.


--
Craig Ringer

pgsql-bugs by date:

Previous
From: "Vladimir Lavrentiev"
Date:
Subject: BUG #4893: Grants on inherited tables checks before constraint exclusion see, that table not needed
Next
From: Craig Ringer
Date:
Subject: Re: BUG #4875: /etc/init.d/postgresql status shows postmaster is stopped when executed as user