|
From: SourceForge.net <no...@so...> - 2006-07-04 16:11:16
|
Bugs item #1517027, was opened at 2006-07-04 18:01 Message generated for change (Comment added) made by markus_gritsch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1517027&group_id=74338 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: MySQL Group: SQLObject release (specify) Status: Open Resolution: None Priority: 5 Submitted By: Markus Gritsch (markus_gritsch) Assigned to: Nobody/Anonymous (nobody) Summary: Exception when using new MySQLdb and UnicodeCol Initial Comment: SQLObject-0.7.1b1-py2.4.egg MySQL Server 5.0 Windows XP SP 2 MySQL-python.exe-1.2.0.win32-py2.4.zip MySQL-python.exe-1.2.1_p2.win32-py2.4.exe The attached test-script 'SQLObject_test.py' works only when using MySQL-python.exe-1.2.0.win32-py2.4.zip, but fails when using MySQL-python.exe-1.2.1_p2.win32-py2.4.exe. The second attachment 'MySQLdb_test.py' which uses MySQLdb directly, works with both versions of the connector. ---------------------------------------------------------------------- >Comment By: Markus Gritsch (markus_gritsch) Date: 2006-07-04 18:11 Message: Logged In: YES user_id=553904 Additional Note: Even if SQLObject can store the unicode string in the DB (and can also retrieve it correctly) when using MySQL-python.exe-1.2.0.win32-py2.4.zip, I think it is stored incorrectly in the DB, because when looking at the value with MySQL Query Browser, it is displayed containing strange characters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1517027&group_id=74338 |
