We are working with 8.1 and migrating to 8.4
We will see if after migration this behavior has disappeared. ;-)
Thank you, Scott.
-Original Message-
From: Scott Marlowe
To: Iñigo Martinez Lasala
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Bad encoded chars in being inserted
Martinez Lasala
Cc: pgsql-admin@postgresql.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 characte
On Mon, Mar 22, 2010 at 2:48 AM, Iñigo Martinez Lasala
wrote:
> Hi everybody.
>
>
>
> I have a doubt about how postgres deal with bad encoded characters into
> database.
>
> We have several gforge application. They are using postgres as database.
>
> If we export a database and import again, we ha
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
Hi everybody.
I have a doubt about how postgres deal with bad encoded characters into
database.
We have several gforge application. They are using postgres as database.
If we export a database and import again, we have to deal with several bad
encoded chars. These bad chars always come from co
