Re: [Sqlalchemy-tickets] [sqlalchemy] #2823: Wrong sqlalchemy.sql.expression.false() / true() compilation when using SQL Server dialect

[sqlalchemy <mi...@zz...>]

#2823: Wrong sqlalchemy.sql.expression.false() / true() compilation when using SQL
Server dialect
-------------------------------------------+-------------------------------
      Reporter:  leavittx                  |      Owner:
          Type:  defect                    |     Status:  new
      Priority:  medium                    |  Milestone:
     Component:  mssql                     |   Severity:  no triage
    Resolution:                            |  selected yet
Progress State:  needs questions answered  |   Keywords:
-------------------------------------------+-------------------------------

Comment (by zzzeek):

 unacceptable!   OK well I'd like to see exactly why sqlalchemy-orm-tree
 generates this.    I'm not sure how comfortable I am doing the collapsing.
 If someone says and_(x=='foo', y=='bar', false(), g==7), it should
 become....what exactly if not the "1=0" thing?   Overall I think that an
 app which is trying to be database agnostic should not be using the
 true()/false() constants at all.  I'm pretty sure SQLAlchemy Core or ORM
 doesn't spit these out anywhere, someone has to use them explicitly.

--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2823#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python