> > i.e. > > session.query([MappedObject.id, > > MappedObject.name]).filter(...).all()
I actually thought of this mapping as well. Only because it seemed consistent with select. Granted I don't understand all the reasons why it could / could not work. That said I'm happy with values as it is, with just a couple of suggestions which I posted on the dev list. > > instead of > > session.query(MappedObject).filter(...).values(MappedObject.id, > > MappedObject.name).all() > > I actually like _values (and _select_from) because it gives you the > option to modify *existing* query. This is useful because you don't > have know everything at the time of query creation (you can write > library functions that operate on user-created queries). It is also > consistent with generative nature of query/select. Except it's not generative itself. :) Michael Trier blog.michaeltrier.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
