Robin Haswell <[EMAIL PROTECTED]> writes: > Hey guys > > It might be a little too late for my app now, but when I was starting > out I decided to use TG's identities. Naturally the TG_User model wasn't > quite what I wanted so I extended it like so: > > class User(TG_User): > > "What is he doing?!" I hear you cry. Yes I did end up with two tables, > with one holding a superset of the data in another. Next time though, > what's the best way to go about this? Maybe TG_User.sqlmeta.addField().. > something like that?
I do the same here. It isolates TG's code from mine and I believe this was better for my application since I can have several "systems" sharing the same user base (TG-wise) with different data. It is a kind of centralized password system :-) Besides, that also makes it easier to adopt another provider (such as LDAP) if I need to. -- 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 -~----------~----~----~----~------~----~------~--~---
