Should have waited 5 minutes before posting that... SqlObjectIdentity.logout is where I got the crazy idea to use the above code for setting the current identity. Plus that should have been user.anonymous = False, not identity.anonymous.
Anyway, does set_current_identity have to take some wacky wrapper around my custom SQLObject class? Why can't it just take the SQLObject instance directly? -- Brian Beck Adventurer of the First Order --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk -~----------~----~----~----~------~----~------~--~---
