One of the patches we have for SQLAlchemy 0.2 support in TG switches from using ActiveMapper for the identity classes to using the straight SQLAlchemy model. The argument that I can see for making that change is that ActiveMapper is an "extension", so it's not quite as supported as the standard data mapper approach. The disadvantage is that it's more verbose and may not be as easy to grok for new users.
What opinions do you all have? BTW, I'm also thinking that we should just remove the identity model classes from saprovider.py, since they're not working anyhow, and just have them in the model.py of quickstart. Kevin -- Kevin Dangoor TurboGears / Zesty News email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
