On Sep 5, 2:14 pm, [EMAIL PROTECTED] wrote: > just a theoretical comment... so instead of relying on SA mapper logic > to automaticaly put the discriminator/s, u are doing it on a level > above, in a way - as SA does not know about the (multiple) > inheritance that those imply. can be useful as an approach for > other 'beyond SA' things... That's right, SQLA is not handling the inheritance directly. In some sense this is nice because there is nothing going on 'under the hood' (at least nothing related to the inheritance structure).
> will it work for multilevel inheritance? I don't think so. This issue did come up but we don't use it in our application so that's ok. I'm not sure how the table joins would work and how the discriminator setting would work. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
