Re: [Sqlalchemy-tickets] [sqlalchemy] #1079: a way to cancel available query.order_by

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

#1079: a way to cancel available query.order_by
---------------------------------+------------------------------------------
    Reporter:  guest             |       Owner:  zzzeek                
        Type:  defect            |      Status:  new                   
    Priority:  medium            |   Milestone:                        
   Component:  orm               |    Severity:  no triage selected yet
  Resolution:                    |    Keywords:  query order_by        
Status_field:  not decided upon  |  
---------------------------------+------------------------------------------
Comment (by zzzeek):

 im pretty strong -1 on this.  Because:

  * what about `filter()`?
  * what about `filter_by()`?
  * what about `options()`?
  * what about `group_by()`?
  * what about `limit()` ?
  * everything else

 The Query's state is non-reversible.   I can't think of any reason why
 `order_by()` would get "special meaning" in this regard and all the other
 methods do not.

 If you need a `Query` that does not have a particular ordering, keep a
 reference to the original `Query` before `order_by()` is applied.

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