Re: character 0xe29986 of encoding "UTF8" has no equivalent in "LATIN2"

From: Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>
To: Andreas Kalsch <andreaskalsch(at)gmx(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: character 0xe29986 of encoding "UTF8" has no equivalent in "LATIN2"
Date: 2009-08-03 22:45:26
Message-ID: 99CAFE78-636A-40B2-91DA-A954DE978CD6@solfertje.student.utwente.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 3 Aug 2009, at 20:32, Andreas Kalsch wrote:

> Problem: Users will enter _any_ characters in my application and an
> error really doesn't help in this case.

I think the real problem is: Where do you lose the original encoding
the users input their data with? If you specify that encoding on the
connection and send it to a database that can handle UTF-8 then you
shouldn't be getting any conversion problems in the first place.

Alban Hertroys

--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.

!DSPAM:737,4a77688810131526383955!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andreas Kalsch 2009-08-03 22:57:05 Re: character 0xe29986 of encoding "UTF8" has no equivalent in "LATIN2"
Previous Message Ilya Urikh 2009-08-03 22:18:41 Re: Problem with Numerics multiplication in C-function