Re: [Sqlalchemy-tickets] [sqlalchemy] #2823: clarify docs regarding true()/false() constants, that these are not fully compatible on many backends (was: Wrong sqlalchemy.sql.expression.false() / true() compilation when using SQL Server dialect)

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

#2823: clarify docs regarding true()/false() constants, that these are not fully
compatible on many backends
---------------------------+----------------------------------
      Reporter:  leavittx  |      Owner:
          Type:  defect    |     Status:  new
      Priority:  medium    |  Milestone:  0.8.xx
     Component:  mssql     |   Severity:  minor - half an hour
    Resolution:            |   Keywords:
Progress State:  in queue  |
---------------------------+----------------------------------
Changes (by zzzeek):

 * severity:  no triage selected yet => minor - half an hour
 * status_field:  needs questions answered => in queue
 * milestone:   => 0.8.xx


Comment:

 the true/false constants are a new thing overall and were to suit some
 usages on Postgresql where the exact expression "IS TRUE/FALSE" is needed.
 I'd prefer if people don't use these constructs otherwise, rather than
 trying to simulate their full effect on backends that don't support it.

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