Hi Ian
Thank you for your response.
It turns out that the problem is not Django related at all, the Legacy
system adds this character 0x81 of some reason to text strings and it seems
like its the Postgres driver that fails to convert this to a UTF8 char. So
its true, i have to purge the data
What is that character supposed to be?
According to the Wikipedia page on CP1252, 0x81 is an unused character
position. There is a mention that it might map to some ISO-2022 control
code with no unicode equivalent.
I'm not sure where the error message is coming from, though -- if it was in
the
Hi all
I'm new Django user. I have a legacy system based on a Postgres 9.1
database that is using encoding WIN1252. When i try to retrie data from one
table I get the following error
>>character 0x81 of encoding "WIN1252" has no equivalent in "UTF8"<< , does
that mean i cant use Django
3 matches
Mail list logo