On Thursday 21. October 2010 22.58.35 Michael Bayer wrote: > On Oct 21, 2010, at 2:39 PM, oystein wrote: > > Hi all, > > > > I am using declarative to model an existing object hierarchy where > > there is an > > abstract part that i model as an hierarchy of mixins and a concrete > > part where > > i use joined-table inheritance. > > > > I have a problem when there is attributes with the same name, one > > overriding > > the other, in the abstract mixin hierarchy. Maybe I am doing something > > wrong > > so suggestions for how to implement this is most welcome. > > Your patch is completely correct in that an attribute on a mixin should > take precedence that of super-class mixins. The story is a little > different for attributes on mapped classes, but that's not an issue here. > The patch leaves existing tests unaffected, and is committed in > r67a7868cfba1 along with a new test...thanks ! >
Thanks for the quick response and the work you put into sqlalchemy! Its impressive to see how you keep up with all the questions on the mailinglist. --- Oystein -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
