From: Gabriele Bartolini <gabriele.bartolini@2ndQuadrant.it>
To: Iñigo Martinez Lasala <imartinez@vectorsf.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Bad encoded chars in being inserted into database
Date: Mon, 22 Mar 2010 22:50:42 +0100
Message-ID: <4BA7E632.1080608@2ndQuadrant.it> (raw)
In-Reply-To: <050f01cac99c$7dafe100$790fa300$@com>
References: <050f01cac99c$7dafe100$790fa300$@com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: gabriele.bartolini@2ndQuadrant.it, imartinez@vectorsf.com
Subject: Re: Bad encoded chars in being inserted into database
In-Reply-To: <4BA7E632.1080608@2ndQuadrant.it>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox