Sanjay wrote: > I feel if turbogears would also support generating SQLAlchemy code > apart from ActiveMapper code, these complexities could be handled > easily. Do you too think same way, can I post a ticket for it?
TurboGears supports straight SQLAlchemy just fine, for the most part. Your problem seems to be that you are telling TurboGears that you want to use the SQLAlchemy identity provider, but then you are subsequently defining your own classes. ActiveMapper goes ahead and declares the tg_user table as soon as the User class from the identity provider is loaded into memory. You are subsequently defining the table again. Clearly, this makes SQLAlchemy mad :) Why don't you just write your own identity provider? This would give you maximum flexibility to do whatever the heck you want, since you seem to need a significant amount of complexity that most people won't ever need (or want). The one that is there is pretty much an exact replacement for the SQLObject provider, and provides the same capabilities that you would expect from the SQLObject one. You could also use the existing identity provider and simply create your more complex model as a separate model entirely (have the regular User class and a special MyUser class that relates back to the User class). This would give you all the complexity you need, and prevent you from having to write your own identity provider. Good luck! -- Jonathan LaCour http://cleverdevil.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
