> im going to play with this a little bit, but my first instinct is
> that you might want to use contains_eager('children.children', ...)
> for your deeper aliases. but im not sure if something might prevent
> that from working since i havent tested contains_eager in self-
> referential scenarios as of yet.
Thanks for taking a look. I did give
contains_eager('children.children') a try as it seemed the most likely
thing to work. Unfortunately it seemed to override the previous
contains_eager relation, so I ended up with the root's 'children'
relation coming up with subnode2 rather than node2 (i.e. skipping the
first relation), but its nice to know I wasn't completely off that
mark :)
Stephen Emslie
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
