Best practice for: ERROR: invalid byte sequence for encoding "UTF8"

From: "Ivan Zolotukhin" <ivan(dot)zolotukhin(at)gmail(dot)com>
To: "Postgres General" <pgsql-general(at)postgresql(dot)org>
Subject: Best practice for: ERROR: invalid byte sequence for encoding "UTF8"
Date: 2007-08-15 11:41:30
Message-ID: 751e56400708150441i49402599re113a3470fbe26a0@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello,

Imagine a web application that process text search queries from
clients. If one types a text search query in a browser it then sends
proper UTF-8 characters and application after all needed processing
(escaping, checks, etc) passes it to database. But if one modifies URL
of the query adding some trash non-UTF-8 characters, database raises
an error: invalid byte sequence for encoding "UTF8".

What is the best practice to process such a broken strings before
passing them to PostgreSQL? Iconv from utf-8 to utf-8 dropping bad
characters?

--
Regards,
Ivan

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dmitry Koterov 2007-08-15 11:41:53 How to trap exceptions inside PL/Perl functions?
Previous Message Torsten Zühlsdorff 2007-08-15 10:28:50 Re: Persistent connections in PHP