bojanb wrote: > >> the solution is the same as that I illustrated in a previous email, that >> when you map to a JOIN you must place all "equivalent" columns which you >> would like populated identically in groups. This is described >> athttp://www.sqlalchemy.org/docs/05/mappers.html#mapping-a-class-agains... > > You're right. Sorry, it just wasn't clear to me that you need to > specify the equivalent columns throughout the whole inheritance > hierarchy. I thoguht that SQLA would somehow automagically know that > they are "equivalent".
it figures that out when you use "inherits", but mapping to the join without using "inherits" it doesn't make any assumptions (since you could be mapping to something more complicated and the "equivalent" logic would start losing stability) > > Thanks a lot for your effort Mike, this was really of great help! we're done, hooray ! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
