bradleyayers/django-tables2 — Issue #55: order_by is always called on a passed query set
Author: mwhudson
Created: 2012-03-07 03:25:13+00:00
State: open

This feels unintentional. But __init__ sets order_by and even if its being set to None, this ends up calling self.data.order_by(()), which ends up calling .order_by() with no arguments on the queryset, which aiui will lose any ordering that has happened to the queryset already. As I said, this doesn't seem right -- have I misunderstood?