From: Iñigo Martinez Lasala <imartinez@vectorsf.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Bad encoded chars in being inserted into database
Date: Tue, 23 Mar 2010 09:11:58 +0100
Message-ID: <1269331918.8928.12.camel@deimos> (raw)
In-Reply-To: <dcc563d11003221505w7a12d704j3d0ce0b50a5f83c0@mail.gmail.com>
References: <AcrJnH1ewzMtxpQ8RNe8stLAPzTRcg==>
<050f01cac99c$7dafe100$790fa300$@com>
<dcc563d11003221505w7a12d704j3d0ce0b50a5f83c0@mail.gmail.com>
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 <scott.marlowe@gmail.com>
To: Iñigo Martinez Lasala <imartinez@vectorsf.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Bad encoded chars in being inserted into database
Date: Mon, 22 Mar 2010 16:05:44 -0600
On Mon, Mar 22, 2010 at 2:48 AM, Iñigo Martinez Lasala
<imartinez@vectorsf.com> 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 have to deal with several bad
> encoded chars. These bad chars always come from copy & paste emails from
> Lotus Notes mail client. OK, I understand the Notes client people is using
> is an ancient application and does not deal very well with some Unicode
> chars…
>
> What I cannot understand is why postgres accept these bad enconded
> characters into database, exports them without problema but does not allow
> them when importing again.
>
> This has been happening since postgers 7.3. However, until 7.4.XX (y don’t
> remember what minor version) you could import database without ERRORs.
> However, since 7.4.XX it’s impossible and it’s imperative to clean bad
> characters (using iconv, for example) prior importing tables.
This is because postgresql's support for UTF-8 encoding (and all
encoding really) has gotten tighter over time, so that the filter to
catch improperly encoded UTF has gotten better with each major
release.
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: imartinez@vectorsf.com, scott.marlowe@gmail.com
Subject: Re: Bad encoded chars in being inserted into database
In-Reply-To: <1269331918.8928.12.camel@deimos>
* 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