Subject | Re: [firebird-python] Progress on kinterbasdb 3.3 |
---|---|
Author | Uwe Grauer |
Post date | 2008-11-22T21:33:42Z |
Pavel Cisar wrote:
I reused my environment LANG to set the connection charset for
connect().
Thanks for the hint!
Why isn't 'UTF-8' a valid db charset name (alias)?
Uwe
> Uwe Grauer napsal(a):Yes, indeed.
>> I get this error with the new version:
>> 'Attempt to look up Python codec name on basis of database char set name
>> failed.'
>>
>> My database character set as reported by flamerobin is "UTF8".
>> my LANG enviroment setting is "en_US.UTF-8".
>>
>> Any hints on why i get this error message?
>
> Well, this error is reported when connection charset is not found in
> DB_CHAR_SET_NAME_TO_PYTHON_ENCODING_MAP dictionary (defined in
> typeconv_text_unicode.py module), so my guess is that you didn't
> specified a valid one. Any chance you have specified UTF-8 instead UTF8 ?
>
> best regards
> Pavel Cisar
> IBPhoenix
I reused my environment LANG to set the connection charset for
connect().
Thanks for the hint!
Why isn't 'UTF-8' a valid db charset name (alias)?
Uwe