Re: [Sqlalchemy-tickets] [sqlalchemy] #2823: clarify docs regarding true()/false() constants, that
Brought to you by:
zzzeek
|
From: sqlalchemy <mi...@zz...> - 2013-10-23 21:52:08
|
#2823: clarify docs regarding true()/false() constants, that these are not fully
compatible on many backends
-----------------------------------+----------------------------------
Reporter: leavittx | Owner:
Type: defect | Status: closed
Priority: medium | Milestone: 0.8.xx
Component: mssql | Severity: minor - half an hour
Resolution: duplicate | Keywords:
Progress State: completed/closed |
-----------------------------------+----------------------------------
Comment (by zzzeek):
this is all completed, so that true/false work in as many cases as
possible (with "IS" still being one that isn't going to work cross-
platform at the moment). true/false will be factored out of and/or, or
will flatten out other elements, and will also render as `1 = 1` or `0 =
1` on non-boolean backends, we'll see how that goes. If true/false aren't
used then you never see their effects.
please see
http://docs.sqlalchemy.org/en/latest/changelog/migration_09.html#improved-
rendering-of-boolean-constants-null-constants-conjunctions.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2823#comment:9>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|