On Mar 1, 2006, at 7:30 PM, Valentino Volonghi aka Dialtone wrote:
assuming the current conversion-in-python works, does that get
the job done for us ? or is there some advantage to psycopg's
extension that we're missing out on ?
Yes it works now, I tried inserting japanese text.
The advantage using psycopg is that it's done in C and using
postgresql APIs. I'm unsure about such an advantage.
well I am sure calling value.decode('utf8') is calling a C function
as well. anyway, if its working now im inclined to leave it as its a
simple across-the-board solution, unless you want to submit a patch
that appropriately pulls in psycopg2's version of the function for
the postgres module, but that seems less than ideal since then you
cant have two simultaneous engine connections to a non-utf and a
utf-8-encoded database.
also note there is a Unicode datatype that can be used on a column by
column basis for this translation as well.
-------------------------------------------------------
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