On Aug 31, 2007, at 6:22 AM, stephen emslie wrote:
>
> so far my only attempt was to filter on more than one alias, but
> contains_eager refers to the statement as a whole and so only only one
> relation can be set against one of the aliases so it doesn't seem
> possible to chain these together.
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.
>
>> I think theres probably some relatively simple options we can be
>> adding to Query here to support what you're trying to do....such as
>> contains_eager('children', alias=myalias, add_columns=True) which
>> would automatically add the columns to the Query's SELECT statement
>> without needing to construct your from_statement() like we're doing
>> above.
>
> This would certainly neaten things up :)
yeah it will require me playing with the example a little bit to
figure out what might be useful here...
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
