470,581 Members | 2,460 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,581 developers. It's quick & easy.

firebird and unicode

Hi,

i'm developing an app that uses wxPython and Firebird via kinterbasdb on
Win XP SP2. On insert of a record i get this error:
(kinterbasdb.InterfaceError)
(0, "Type mismatch: Input parameter for field named [name n
ot known at this stage of query execution] must be a string, rather than
a <type 'unicode'>.")

Python, wxPython are all unicode enabled. The firebird database is
created with the UNICODE_FSS charset and opened as such in kinterbasdb's
connect function (charset=UNICODE). The GUI's charset is made with
wxGlade and there i specified UTF-8 for the encoding.

I'm out of ideas as to why i get this error message.

Any ideas?

Thanks
Benedict
Jul 19 '05 #1
3 1963
flupke wrote:
Hi,

i'm developing an app that uses wxPython and Firebird via kinterbasdb on
Win XP SP2. On insert of a record i get this error:
(kinterbasdb.InterfaceError)
(0, "Type mismatch: Input parameter for field named [name n
ot known at this stage of query execution] must be a string, rather than
a <type 'unicode'>.")

Python, wxPython are all unicode enabled. The firebird database is
created with the UNICODE_FSS charset and opened as such in kinterbasdb's
connect function (charset=UNICODE). The GUI's charset is made with
wxGlade and there i specified UTF-8 for the encoding.

I'm out of ideas as to why i get this error message.

Any ideas?

Thanks
Benedict


If looked around a bit and it seems i have to do a
kinterbasdb.init(type_conv=100). But this gives another error:

File "C:\Python24\lib\site-packages\kinterbasdb\__init__.py", line 343,
in init
fakeFunc.func_code = realFunc.func_code
ValueError: Date() requires a code object with 0 free vars, not 1

I installd the mx Data time module and the fixedpoint module but that
doesn't help. I still get the same error.
Does anybody know what's wrong?

Thanks,
Benedict
Jul 19 '05 #2
flupke wrote:
<snip>

I solved it by getting the latest py files from CVS and overwriting the
existing ones. It gave an Attribute error but that was gone after
commenting this line:
#isc_info_isc_version = _k.isc_info_isc_version

I'm not sure if this is a safe way of working. It's like jumping over a
fence with barb wire. You know your balls might be in danger but
sometimes you got to take a risk :)

I hope i don't end up singing with a funny voice ;)

Thanks,
Benedict Verheyen
Jul 19 '05 #3
Le Mon, 23 May 2005 09:30:31 GMT, flupke a écrit :
It's like jumping over a fence with barb wire.
You know your balls might be in danger but
sometimes you got to take a risk :) +1 QOTW

I hope i don't end up singing with a funny voice ;)

Jul 19 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.

By using this site, you agree to our Privacy Policy and Terms of Use.