-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jason Chu wrote: > I'm in the midst of trying to deploy our first public release and I'm > running into a problem that has been mentioned before. > > Every time I try to log in, the byUserId (or by_user_name) query > generated by identity fails with this traceback: [...]
I had exactly the same problem, which made me waste a lot of time. I've disbled the decoding filter in CherryPy for now. I analyzed the problem like this: - - form values get returned as Unicode strings - - SQLObject does its own parameter quoting and inserting instead of relying on the DB-API module - - in Python ascii_string % unicode_string always returns a Unicode string - - so, a Unicode string gets sent to the DB-API module as SQL command - - this does *not* work with all DB-API modules - - in particular not with psycopg1, which I'm using I only saw three possibilities: - - patch psycopg (but then it needs to know the target encoding) - - patch SQLObject (worked, but I don't want to maintain local patches) - - disable CherryPy decoding filter - -- Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFERWGGdIO4ozGCH14RAkP3AJsH3MVgL0quGZ2S+zjUPotPaFXesQCfVX82 gnjv40203OWLTXvQcldb2OM= =8dCl -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
