> > This isn't entirely true. In case you introduced new objects (and adding > > identity should do that), this shouldn't cause any problems. > > > > Of course you need to copy'n'paste the model classes for identity from > > e.g. a freshly created project. But beyond that, you're finished. > > I'm not entirely sure what you're saying here, Diez. My understanding > is that at a minimum, his tg_user object will change, requiring a > manual update of the database schema for that object, based on whatever > the fresh project generates as the relevant columns. This is on top of > the cut/paste of Python code for the model. I am assuming that the > entirely new tables for new model objects will be added automatically.
But where do you see the tg_user object come from, without prior usage of identity? Maybe I'm missing something here, but AFAIK there is no such object in a non-identity-project. Which purpose would it serve anyway, when the identity system isn't in place and thus you can't log in to make a difference. Diez --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
