[sqlalchemy] Re: Extended Query subclass with add_named_column method

2009-03-31 Thread Michael Bayer
wouldn't this be accomplished more simply using contains_eager() ? On Mar 31, 2009, at 9:12 AM, Bob Farrell wrote: Hello, SQLAlchemy people, So I spoke to jek on IRC to see if there was a way to use add_column without causing the query to return a RowTuple and it doesn't look like there

[sqlalchemy] Re: Extended Query subclass with add_named_column method

2009-03-31 Thread Bob Farrell
Yes, if this has been defined on the mapper. Generally I do a lot of just using SQLAlchemy to as a way of writing SQL in Python code that can be passed around for dynamically building up queries so my mappers tend to be quite bare - or are you suggesting this can be done without configuring the

[sqlalchemy] Re: Extended Query subclass with add_named_column method

2009-03-31 Thread Michael Bayer
no, you'd need the mapping to be set up.So yes, if you need to compose your result objects together in some way that is specific to your use case and has no relationship to your mappings or any standard SQLAlchemy feature, you need to either post-process the result of Query or create