> I don't know where the bugreport is, but you can avoid lots of issues
> that way:
>
> 1. Upgrade to MySQLdb-1.2.2
> ('cause there is another unicode-issue in 1.2.1)
Done
> 2. let MySQL always use UTF-8/unicode
> (if you cannot change defaults on your MySQL you can try the
> corresponding connection parameters; some of
> charset=utf8&sqlobject_encoding=utf-8&use_unicode=1)
Done as mentioned above
> 3. easy_install SQLObject==bugfix
> (Will pull SQLObject 0.7.5 from SVN. You won't get happy with
> SQLObject 0.8, so if you don't like 0.7 go ahead to 0.10)
Done ( my code will include the latest version available. wont it?
cause 0.7 is still in site-packages)
> 4. in "sqlobject/mysql/mysqlconnection" remove lines 31-34 (including)
> to let SQLObject have your querries pass directly to MySQLdb as
> they are delivered - in Unicode
>
When i comment out the lines u say i get error's on app startup
Maybe u can post the exact lines????
The problem insists....
> I run a rather complex application with characters from several
> alphabets without any MySQL-related issues anymore. Give it a try.
>
Do u use Binary columns in u r app?? Because this is where i get the
problems
> If someone knows a better solution to point 4, let me know please.
>
> -- Mark
With
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
