Обсуждение: BUG #2175: 22021: invalid byte sequence for encoding \"UNICODE\":
The following bug has been logged online: Bug reference: 2175 Logged by: Roberto Email address: speedrob@pop.com.br PostgreSQL version: 8.0 Operating system: windows XP Description: 22021: invalid byte sequence for encoding \"UNICODE\": Details: when I go to insert one string with accent in the bank of the following o error: 22021: invalid byte sequence for encoding \"UNICODE\":
Re: BUG #2175: 22021: invalid byte sequence for encoding \"UNICODE\":
От
tomas@tuxteam.de (Tomas Zerolo)
Дата:
On Mon, Jan 16, 2006 at 11:55:12PM +0000, Roberto wrote: >=20 > The following bug has been logged online: >=20 > Bug reference: 2175 > Logged by: Roberto > Email address: speedrob@pop.com.br > PostgreSQL version: 8.0 > Operating system: windows XP > Description: 22021: invalid byte sequence for encoding \"UNICODE\": > Details:=20 >=20 > when I go to insert one string with accent in the bank of the following o > error: > 22021: invalid byte sequence for encoding \"UNICODE\": This usually means that the encoding of your client is not UTF-8. Try some query like "SET client_encoding TO 'LATIN1'" to see if the problem disappears. Better yet -- try to convince the client to use UTF-8 encoding. HTH -- tomas