Hi, >I don't think the Active Record pattern is a bad design practice for >*all* applications, only for ones where there are significant >divergence between the the "database design details" and the preferred > > Likewise, I think ActiveRecord is appropriate for most web apps.
I do have concerns about Elixir, because it's very different in style to SQLAlchemy. In many ways I liked ActiveMapper better, as it was a thinner layer, and it seemed more natural to mix ActiveMapper with plain SA mappers. But right now Elixir is the only actively-maintained Active Record layer for SA. In principle I think we need the following: The core of TG (i.e. config and request transaction wrapping) works as long as you use SessionContext (so assignmapper, ActiveMapper, Elixir all just work). (and in fact the config bit doesn't even need SessionContext). QuickStart model.py needs both a plain SA-ORM (possibly assignmapper) mode, and an Elixir mode Most of identity works with SA-ORM (so Elixir, etc. just work); the quickstart bit has two modes. FastData/CatWalk works with SA-ORM, so Elixir etc. just work. In fact, we've already got a lot of that. But this doesn't answer the basic question: what should the default be? Another way to put this is: how would we like the Wiki20 tutorial to show people to do things? My vote is for Elixir. Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
