We were having problems with SQLObject on our production Red Hat Enterprise Linux 5 Servers but not on our development Fedora 9 boxes. After some searching I tracked it down to a difference in the MySQL-python modules. The RHEL5 boxes have MySQL-python-1.2.1 and the Fedora boxes have 1.2.2. The 1.2.2 version has a change that allows the query string to be sent as either a unicode string or a byte string while the 1.2.1 version will fail if it's a byte string.
I looked at the SQLObject source and found that SQLObject used to change the query into a byte string but that's no longer the case. The relevant revisions are svn diff -r 3021:3022 which removes the functionality and the chunk of svn diff -r 3175:3176 that removes self.need_unicode (as it was no longer used). If it was removed just because someone thought it wasn't necessary (without thinking about old versions of MySQL-python) I'd be happy to submit a patch which converts to unicode if the MySQL-python version >=1.2.1 < 1.2.2. if there's another reason, please let me know. -Toshio
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
