On Jan 27, 2007, at 11:57 AM, Allen Bierbaum wrote:
> As a side note, I am trying to see where ActiveMapper would fit into > all of this. At first I thought that ActiveMapper would actually tie > the classes closer to the data model, but after looking at it further > I am starting to think that it still has all the power and flexibility > of the other methods of using SA but simple encapsulates the Table and > Mapper creation in a single unit. Can anyone tell me if this is a > correct assessment? there is a project going on involving ActiveMapper and TurboEntity combining to make the next generation of "declarative" layer. the current ActiveMapper is quite minimal. i think its getting time for them to talk about it a little bit. personally I think ActiveMapper complicates things and also requires that the entire SA api be rewritten, as most ActiveMapper issues refer to SA features that are not available through its interface. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
