You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixed bug where :meth:.Table.update and :meth:.Table.delete
would produce an empty WHERE clause when an empty :func:.and_()
or :func:.or_() or other blank expression were applied. This is
now consistent with that of :func:.select.
fixes Empty OR clause with table.delete() produces invalid SQL #3045
Fixed bug where :meth:.Table.update and :meth:.Table.delete
would produce an empty WHERE clause when an empty :func:.and_()
or :func:.or_() or other blank expression were applied. This is
now consistent with that of :func:.select.
fixes Empty OR clause with table.delete() produces invalid SQL #3045
Activity
sqlalchemy-bot commentedon May 9, 2014
Michael Bayer (@zzzeek) wrote:
.Table.update
and :meth:.Table.delete
would produce an empty WHERE clause when an empty :func:
.and_()
or :func:
.or_()
or other blank expression were applied. This isnow consistent with that of :func:
.select
.fixes Empty OR clause with table.delete() produces invalid SQL #3045
→ 55eacc8
sqlalchemy-bot commentedon May 9, 2014
Michael Bayer (@zzzeek) wrote:
.Table.update
and :meth:.Table.delete
would produce an empty WHERE clause when an empty :func:
.and_()
or :func:
.or_()
or other blank expression were applied. This isnow consistent with that of :func:
.select
.fixes Empty OR clause with table.delete() produces invalid SQL #3045
→ 93e11a9
sqlalchemy-bot commentedon May 9, 2014
Changes by Michael Bayer (@zzzeek):
sqlalchemy-bot commentedon May 9, 2014
Michael Bayer (@zzzeek) wrote:
thanks