> > > this is not OK since you'll get a cartesian product from A and Node. > > that's exactly what i intended. >
I'm not sure I see of what use that is. An implicit join *would* be useful, though, and it's a much bigger usecase. I can see "explicit only" in the select() construct, because two database rows can have a lot of potential join points between them, and sqla shouldn't try to guess. But the situation with mapped objects is a bit different, as the joinpoints have already been explicitly enumerated by the author of the extant mappers in place. One of the big benefits of Query() + eagerload() and it's friends is the abillity to capture and reuse that relational information. Right now, it seems clumsier than it ought to be to join two mapped instances together. There is a raft of duct tape like "add_column()", and "add_entity". The basic functionality is there, but the interface is kind of clunky. Maybe I'm a bit hung up on the "Query() as mapper-aware select()", but it is a pretty damned elegant idea. Just my 2c - you wanted feedback :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
