On 10/25/05, Jeff Watkins <[EMAIL PROTECTED]> wrote: > I still have to address folks like yourself who have alternate model > requirements -- there should be a way to tell the TurboGears identity > module what model classes to use.
Is this your proposed solution for cases where we need "users+" objects? Currently, I'm using a homegrown identity/authentication/authorization, but it's not as nice as turbogears.indentity. The only reason I haven't switched is that I have a pile of additional columns currently in my User object. The solution I was going to implement is have two tables--identity's User and my own UserData, and just look up UserData.byUser() every time, but that seems awkward. -- Tim Lesher <[EMAIL PROTECTED]>
