Message-ID: <4BA7E632.1080608@2ndQuadrant.it>
Date: Mon, 22 Mar 2010 22:50:42 +0100
From: Gabriele Bartolini <gabriele.bartolini@2ndQuadrant.it>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: =?windows-1252?Q?I=F1igo_Martinez_Lasala?= <imartinez@vectorsf.com>
CC: pgsql-admin@postgresql.org
Subject: Re: Bad encoded chars in being inserted into database
References: <050f01cac99c$7dafe100$790fa300$@com>
In-Reply-To: <050f01cac99c$7dafe100$790fa300$@com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

Hi,
>
> I agree with this postgres policy, but what I don’t is that you can 
> INSERT them via application. That is, no bad characters should be 
> inserted into database. The check should be made for both import and 
> insert procedures so no bad chars would appear into database.
>
Could you please tell us which PostgreSQL version you are currently 
using? Also it would be useful to know:

* which is your database encoding?
* which is the client_encoding setting you are using?

In general, what you are saying suggests me that you are using the 
SQL_ASCII encoding at some stage in your session (either on the server 
side or the client side).

However, before I go on, please answer the above questions.

Thanks,
Gabriele

-- 
 Gabriele Bartolini - 2ndQuadrant Italia
 PostgreSQL Training, Services and Support
 gabriele.bartolini@2ndQuadrant.it | www.2ndQuadrant.it