Re: [Sqlalchemy-tickets] [sqlalchemy] #2804: coerce_to_bool for where(), having(), etc.

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

#2804: coerce_to_bool for where(), having(), etc.
------------------------------+-------------------------------
      Reporter:  zzzeek       |      Owner:  zzzeek
          Type:  enhancement  |     Status:  new
      Priority:  medium       |  Milestone:  0.9.0
     Component:  sql          |   Severity:  major - 1-3 hours
    Resolution:               |   Keywords:
Progress State:  in queue     |
------------------------------+-------------------------------

Comment (by zzzeek):

 heh, see also #2823 where I'm saying that we *don't* want to do this,
 though sort of looking at it differently.

 true/false on a system that doesn't support t/f, it's going to be 1 or 0.
 If we say that any boolean type including true/false that is evaluated in
 any kind of context that is *not* a comparison just becomes "<val> == 1",
 that might be a solution for this and also #2823.

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