Re: Bad encoded chars in being inserted into database

From: Iñigo Martinez Lasala <imartinez(at)vectorsf(dot)com>
To: Gabriele Bartolini <gabriele(dot)bartolini(at)2ndQuadrant(dot)it>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Bad encoded chars in being inserted into database
Date: 2010-03-23 08:10:16
Message-ID: 1269331816.8928.10.camel@deimos
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Postgresql version: 8.1.13 (8.1.13-0etch1)
database encoding: UTF-8.
client_encoding: default, that is, it's no set at php level.

However, pg_client_encoding returns "UTF8" as client encoding.

Thank you, Gabriele.

-----Original Message-----
From: Gabriele Bartolini <gabriele(dot)bartolini(at)2ndQuadrant(dot)it>
To: Iñigo Martinez Lasala <imartinez(at)vectorsf(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] Bad encoded chars in being inserted into database
Date: Mon, 22 Mar 2010 22:50:42 +0100

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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Iñigo Martinez Lasala 2010-03-23 08:11:58 Re: Bad encoded chars in being inserted into database
Previous Message Tom Lane 2010-03-22 23:07:35 Re: Disparity between 8.1.18 and 8.2.14 performance wise