Hey,
New problem :-) I have two TG environments at the moment, one
development one user acceptance test. On test I have SQLObject 0.8.3
and uat I have SQLObject 0.7.7 (I'm working to get both envs the
same).
I have always been using sqlite for dev, but will need to move to
MySQL. When I made this switch I instantly got an exception in dev:
[...snip...]
File "/usr/lib64/python2.4/site-packages/MySQLdb/connections.py",
line 136, in __init__
self.charset = self.character_set_name().split('_')[0]
File "/usr/local/lib64/python2.4/site-packages/SQLObject-0.8.3-
py2.4.egg/sqlobject/mysql/mysqlconnection.py", line 65, in
character_set_name
return encoding + '_' + encoding
TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'
So, I compared why uat was working and dev wasn't. It looks like some
code has been changed with respect to MySQLdb < 1.2.1 hack. I'm
running MySQLdb 1.2.0-17.2 which means I'm running the exception code.
Basically to get it to work I had to add in the "if self.dbEncoding:"
sections again to skip that code.
I need to check the SQLObject changelogs to try and find the rational
for this, but has anyone else hit this error?
Thanks!
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
