On Oct 14, 2011, at 10:56 AM, Burak Arslan wrote: > On 10/14/11 06:40, Michael Bayer wrote: >> its a little awkward but if you use bindparam() in the inner select, >> query.params() can access those parameters just fine, you'd just need to use >> it in all cases. >> >> there's some related example of doing this with a relationship at >> http://www.sqlalchemy.org/trac/wiki/UsageRecipes/GlobalFilter . > > hi michael, > > thank you very much for the reply, your suggestion solves my issue. > however, I do agree that it's a little bit awkward to have to remember a > params() after a .filter(), is there any reason for not unifying them?
how would a unification of filter() and params() look ? filter() expresses expression structures, and params() the values. You can use just filter() with literal values and they are converted into bind params automatically. just not clear what you mean here. -- 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.
