0.4.7 and above supports query.values(col1, col2, ...) . use that.
Bobby Impollonia wrote: > > Yeah, with .4 there isn't really a way have an ORM query that doesn't > select at least one ORM object (possibly with additional columns/ > objects added via add_column/ add_entity). You can use the select() > construct instead if pulling all the columns of the mapped class is > unacceptable. > > On Wed, Nov 19, 2008 at 1:25 PM, Moshe C. <[EMAIL PROTECTED]> wrote: >> >> 0.4.6 >> >> On Nov 19, 11:12 pm, "Bobby Impollonia" <[EMAIL PROTECTED]> wrote: >>> What version of SQLA are you using? In .5 , you can pass individual >>> columns instead of a mapped class to session.query. >>> >>> On Wed, Nov 19, 2008 at 12:17 PM, Moshe C. <[EMAIL PROTECTED]> wrote: >>> >>> > For Query there is an add_column() method, but I do not see a remove >>> > column method. >>> > Initializing a Query requires a full mapped class, so how can I >>> select >>> > on only a subset of the columns. >>> >>> > I want to do this for ding a DISTINCT query on only a couple of >>> > columns. >>> >>> > TIA >>> > Moshe >> > >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
