Robin Haswell <[EMAIL PROTECTED]> writes: > 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.
Yes, it is, but you'd have to change the model identity will use to your own model. This way you'll have to update your model if something on identity changes. If you choose inheritance, you'll end up with two tables being related. > 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. I don't remember if you can change that but a look at config.py will probably show you if it is a configuration option. I believe that if you declare another field as the PK on your model it will be used by default. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
