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: Bad encoded chars in being inserted into database |
Date: | 2010-03-22 21:50:42 |
Message-ID: | 4BA7E632.1080608@2ndQuadrant.it |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(dot)bartolini(at)2ndQuadrant(dot)it | www.2ndQuadrant.it
From | Date | Subject | |
---|---|---|---|
Next Message | Dai, Tino | 2010-03-22 21:58:41 | Disparity between 8.1.18 and 8.2.14 performance wise |
Previous Message | Scott Mead | 2010-03-22 18:09:20 | Re: Store database users in custom table |