Re: [Sqlalchemy-tickets] [sqlalchemy] #2668: auto_correlate fails if all froms are existing in a superquery

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

#2668: auto_correlate fails if all froms are existing in a superquery
-----------------------------------+----------------------------------
      Reporter:  lukecyca          |      Owner:  zzzeek
          Type:  defect            |     Status:  new
      Priority:  medium            |  Milestone:  0.8.0final
     Component:  orm               |   Severity:  minor - half an hour
    Resolution:                    |   Keywords:
Progress State:  not decided upon  |
-----------------------------------+----------------------------------

Comment (by zzzeek):

 yeah, that was the other way I thought of too, and I do like that
 approach, that's probably how correlate()/correlate_except() should work.
 But it's a more significant behavioral change.  I'm not thinking of any
 major surprises due to it unless someone has unit tests that are asserting
 a select() with correlate() on it by itself produces certain SQL.   We're
 right at the edge of 0.8 final and I've already run through the betas,
 what do you think ?   I'm inclined to go for it, if things don't obviously
 break within the existing tests.

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