On Wed, Jan 8, 2014 at 3:31 PM, Wichert Akkerman <wich...@wiggy.net> wrote:
> > On 08 Jan 2014, at 01:26, limodou <limo...@gmail.com> wrote: > > > But I don't know why make this decision. Because "where NULL" will get > nothing. And in 0.8.X version, I need to combine multiple condition > according user input to one condition, so my code just like: > > > > cond = None > > for c in conditions: > > cond = c & cond > > Why don’t you change the initial value to true() instead of None? If I > read the documentation correctly that should work correctly in both > SQLAlchemy versions. > > Even cond='' is correctly also, but I just think NULL is not a valid condition expression in SQL, so I think the old appoach maybe better. -- I like python! UliPad <<The Python Editor>>: http://code.google.com/p/ulipad/ UliWeb <<simple web framework>>: https://github.com/limodou/uliweb My Blog: http://my.oschina.net/limodou -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
