it still is needed if you explicitly need an alias() of your SELECT statement. joining to it, embedding it within aliased(). haven't figured out yet if there's some way to make it "automatic" in all cases or if thats appropriate.
also more controverially im thinking of adding a .c. to Query. but we'll see if that use case arises first. On Jan 27, 2009, at 4:34 PM, Jon Nelson wrote: > >> im committing something that will make that exact phrase work (its in >> rev 5734). using a released version of SQLA, for now say >> id.in_(query.statement). > > I took at look at those changes and they look awesome! If I understand > the changes correctly, however, then I wonder what purpose subquery() > has. > > -- > Jon > > > --~--~---------~--~----~------------~-------~--~----~ 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 sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
