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:
-------------------------------------------+-------------------------------
Changes (by zzzeek):

 * priority:  high => medium
 * status_field:  awaiting triage => needs questions answered


Comment:

 SQL server doesn't have "true" or "false" constants so you can't refer to
 them in isolation of a comparison.    otherwise, what SQL would you like
 the expression `or_(true(), false())` to produce on SQL server ?   There
 are of course hacks like "1==1" "1==0" and stuff like that but we prefer
 to do as few of those as possible (the only one we do is the IN () hack,
 which already confuses everyone).

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