Re: [Sqlalchemy-tickets] [sqlalchemy] #2750: Inconsistent behavior for polymorphic queries

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

#2750: Inconsistent behavior for polymorphic queries
-----------------------------------+----------------------------------
      Reporter:  schlamar          |      Owner:  zzzeek
          Type:  defect            |     Status:  closed
      Priority:  high              |  Milestone:  0.8.xx
     Component:  orm               |   Severity:  minor - half an hour
    Resolution:  fixed             |   Keywords:
Progress State:  completed/closed  |
-----------------------------------+----------------------------------
Changes (by zzzeek):

 * status:  new => closed
 * resolution:   => fixed
 * status_field:  needs tests => completed/closed


Comment:

 it's a warning, as apps can successfully work using this technique even
 though it's ill-advised, but also it might be possible to have systems
 where the incoming query and outgoing value are different, even though in
 that case we usually don't have a polymorphic_setter involved.


 read7d9a680911606820dd9c6688fc7131b1a911e 0.8

 r3b24ccaf28fd85a6e54a master

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