On Tue, Nov 27, 2007 at 03:17:23PM +0100, Markus Gritsch wrote:
> Instead of getting an exception, the
> code just continues to run, issuing a query containing the wrong
> characters for the DB.
[skip]
> But I doubt that the BLOB would be inserted *correctly* if it gets
> converted to unicode using the specified encoding. IMO it would be
> desired to insert the BLOB as it is, without trying to decode it.
This is the central part of the problem. Nobody knows for sure how
different versions of MySQL and MySQLdb work according to unicode,
encodings and BLOBs. Someone has to investigate (looking into code, docs,
writing a number of test programs for a number of MySQL+MySQLdb variants).
It could be the entire "need_unicode" in SQLObject is wrong.
Oleg.
--
Oleg Broytmann http://phd.pp.ru/ [EMAIL PROTECTED]
Programmers don't die, they just GOSUB without RETURN.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
