That seems a little silly me to me, I can't think of any situations
where I would want two tables holding the same data. Is it possible to
make it so I can extend TG_User yet only end up with one table? I'd like
to extend TG_User for forwards compatability reasons.

Also, on a related note, do identities require that the username field
is called userId? I'd prefer my User class to follow my naming scheme
used elsewhere in the site if possible.

Cheers

-Rob

Max Ischenko wrote:
>>Yes I did end up with two tables,
>>with one holding a superset of the data in another.
> 
> 
> That's perfectly OK and as expected.
> 
> TG_User is declared as InheritableSQLObject and that's the way
> inheritance works in SQLObject.
> 
> Personally, I do not like it and create my own User class that does not
> inherit from TG_User but merely copies some of the attributes used by
> framework, like userId and emailAddress.
> 
> HTH,
> Max. // http://maxischenko.in.ua.
> 
> 
> 

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to