On 4/10/06, Brian Beck <[EMAIL PROTECTED]> wrote: > > 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?
I may be wrong (I'm far from authoritative when it comes to Identity's implementation), but it looks like you can send your object into set_current_identity. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
