this is interesting, but what would prevent the same result by creating different mappers for a single class using entity_name ? thats the current way to persist multiple objects of the same class in different ways.
On Mar 21, 2007, at 1:15 AM, Benno Rice wrote: > So one thing we're attempting to do in a project I'm working on is > partitioning our data set across several databases based on object > keys. I've come up with a way to implement this in SQLAlchemy which > I've provided here as a mostly-complete patch. > > Session objects now have a bind_func method which associates a > function taking a mapper and an ORM object and returning a > Connectable to a mapper. When a transaction is begun on an object > associated with that mapper, this function is called in order to work > out which Connectable should be used to handle this object. > > The main area where I haven't been able to work this through > completely is in the dependency handling of many-to-many > relationships. > > I'm very interested in what people think of this and whether they > feel it's a candidate for inclusion in SQLAlchemy. > > The patch is against SQLAlchemy 0.3.5. > > > > > > <sqlalchemy-partitioning.patch> > > -- > Benno Rice > [EMAIL PROTECTED] > http://jeamland.net/ > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
