Re: [Modeling-users] type('') and unicode
Status: Abandoned
Brought to you by:
sbigaret
|
From: SoaF at H. <so...@la...> - 2003-07-16 21:48:15
|
Sebastien Bigaret wrote: > >This needs investigation. If some of you could provide working python >code with unicode and psycopg/pypgsql/pgdb/mysqldb/sqlitedb, please >share. I've not time for this now. > =20 > I don't have some working code since I resolve this by calling a=20 XMLUtils.unicode2Str() .. before doing the request .. :( >However, speaking of case-insensitive match: if postgresql supports it, >then it should work, since the SQL WHERE clause behind is UPPER(...) >LIKE UPPER(...) --pure theory and not tested, so if someone feels like >testing it, go ahead :) > > >-- S=E9bastien. > =20 > In fact I think this is a MySQL dependant since I don't manage to put=20 anything unicode in the database (even without modeling and with latest MySQLDB ) .=20 Something else be carefull that "=E9=E9" isn't a unicode only . So i think the DBA do s= ome=20 translation to utf-8 on the fly ( so it works) Bye Bye |