On Sep 3, 8:25 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > You can certainly map to any of the hierarchies indicated in that > article, but you wouldn't be able to take advantage of SQLA's > "polymorphic" capabilities, which are designed to only handle single > inheritance. You'd really want to make your Engineer(Employee, > Citizen) class and just map it to > engineers.join(citizens).join(employees). That would get your schema > going, just without SQLA having any awareness of the "inheritance" > portion of it, and is extremely similar to a plain concrete setup, > which is pretty much all you'd get anyway without the ability to load > polymorphically. >
Michael, what would the mapper function look like if it were to map Engineer(Employee, Citizen) to engineers.join(citizens).join(employees). What argument of the mapper would that join condition be in? I think concrete inheritance might be the way to go about things, at the cost of the nice polymorphic loading features. Thanks, Sam --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
