Ischenko wrote: > > user= user_class.by_user_name( user_name ) > > There was a bug in 0.9a5 related to using non-ascii username with > identity.
The username does not have any non-ascii characters in it. > > I would advice to wait a couple of days for 0.9a6 to see if it helps. > I downloaded r1454 from svn and installed. I repeated my earlier excersize and found the same error. > Regards, > Max. I did some poking around in the python shell and was able to reproduce the error. I found that, with psycopg2, cursor.execute(sql) will fail if the database has encoding set to unicode and sql is a unicode string. It will succeede if sql is a plain string. If the database is sql_ascii encoded, it does not matter if the sql query is a unicode string or a plain string. The queries produced by sqlobject are obviously unicode strings. This seems backwards. Am I misunderstanding the meaning of creating a database with utf8 encoding? Maybe this is a more appropriate question for the SQLObject/Psycopg/PostgreSQL folks? BTW, I did not have this problem with TG 0.9a1, even though i was using the same rev of SQLObject. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
