On Apr 17, 2006, at 5:47 AM, Vasily Sulatskov wrote:
In my opinion that's a bug and that behaviour should be changed to
something
like that:
1. If object is unicode then convert it to engine specified
encoding (like
utf8) as it happens now
2. If it's a string then convert it to unicode using some another
specifed
encoding (it should be added to engine parameters). This encoding
specifies
client-side encoding. It's often handy to have different encodings
in database
and on client machines (at least for people with "alternate
languages" :-)
there already is an encoding parameter for the engine.
http://www.sqlalchemy.org/docs/dbengine.myt#database_options
does that solve your problem ?
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
