yeah, its committed right now as built in, but its only a handful of lines
of code. if you wanted to bypass it you could call
mapper.select_whereclause() which is what select() calls anyway.
but yah, i think i want to make it optional. i think per-mapper is one
way it might be used; but i think
Michael Bayer wrote:
Ive integrated it with the mapper, which is quite a small change, just
added to select() (when used with a "where" clause, not if you send it a
full Select object) and select_by(). the major thing you lose with this
approach is that you cant call len() on a returned result s
Ive integrated it with the mapper, which is quite a small change, just
added to select() (when used with a "where" clause, not if you send it a
full Select object) and select_by(). the major thing you lose with this
approach is that you cant call len() on a returned result set. I tried
having __
see that everyone ? not so hard :)
Jonas -
this has been high on my list. im attaching this patch to the ticket,
which was not viewable until now since I forgot to press "submit" on it
three days ago. http://www.sqlalchemy.org/trac/attachment/ticket/142
i have also been thinking of having ava
4 matches
Mail list logo
