"multilevel" sounds like you mean this: class A:
class B(A): class C(B): class D(C): That's supported fully in all cases, and for single/joined should work without any special steps (for concrete its slightly more weird). If this is not working then we can get you going with some test cases. If OTOH you mean : class A: tablea class B: tableb class C(A, B): tablec + (tableb join tablea) That's "multiple" inheritance. that is not supported in terms of table mappings that are "multiply" inherited. (Mixin classes, that is where only one of each base is mapped to a table, is encouraged, though). That feature is not likely to be supported directly as it goes way beyond what the architecture does right now and is a really rare, arguably impractical (due to all the joins), use case. You can of course approximate setups like that using relationship(). On Aug 11, 2011, at 5:04 AM, Fayaz Yusuf Khan wrote: > I was trying to configure a multilevel inheritance mapping (either using > joint- > table or single-table) but it didn't work as I was expecting it to. > I understand that it probably has never been thought of, but in my particular > use case, it would have been really handy. > Any idea if this is possible||makes sense? > -- > Fayaz Yusuf Khan > Cloud developer and designer > Dexetra SS, Kochi, India > fayaz.yusuf.khan_AT_gmail_DOT_com > fayaz_AT_dexetra_DOT_com > +91-9746-830-823 -- 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.
