Micheal Bayer wrote:
id rather just add another plugin point on MapperExtension for this, which takes place before the "polymorphic" decision stage at the top of the _instance method, like get_polymorphic_identity(). that way you could do all of this stuff cleanly in an extension (and id do that instead of making polymorphic_identity into a list). hows that sound?
That would be ideal for me, and would seem to be the most flexible solution as well - it leaves the decision for which class to use up to the application. What would it actually return, though? An instance ready to be populated? Thanks a lot, Simon --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
