What I ended up doing for that project was actually leaving the
repoze.who/what tables alone and created a parallel table with my
data. That way, my schema changes wouldn't affect auth. On another
project I let the AuthUser model alone, but, defined my own definition
and set:
__table_args__ = {'useexisting':True}
allowing one table for auth and metadata without having to modify the
default models. Personally, I feel that both approaches are probably
incorrect and with Pyramid, I have overloaded AuthUser with my own
model so that I only need to do one fetch each time there is an auth
request and all extended data is present in the session (with a little
modification).
While each are probably valid approaches, the indirection of the first
two probably would confuse an external developer making modifications
or troubleshooting more difficult.
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" 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/pylons-discuss?hl=en.
