On Mar 21, 2007, at 8:32 PM, Benno Rice wrote:
> > > > What would be nice is a way to do this kind of farm-out in a way that > didn't as much help from higher layers. I can provide the system > with a function that will take an object key and return which engine, > metadata or table object I want to use, I just need a way to glue it > into SQLAlchemy without having to specify it every time I make a call > to my Session object. Do you have any suggestions of how I might > approach this? > > -- well the entity_name approach should also solve your many-to-many problem. cant a thin layer of abstraction be built on top of mapper () and session() so that your object approach internally uses the entity_name concept ? id like to avoid building more complexity into SA's core, both for API documentation reasons as well as maintenance. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
