You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Meaby i have missed out, but i can't find the order attribute
i guess will be better if the columns supports admin_order_field in costume columns method
The text was updated successfully, but these errors were encountered:
Might be, but I wouldn't make it a priority, after all the default sorting is defined by the implementation of aggregate(), other sort are performed at runtime by clicking on the columns header.
My primary concern about sorting is #4, as of the nature of HTTP it's not plain to reuse the result of aggregate() for further data elaboration and it must be recalculated completely every time, even for a simple sort or export. A client side approach could be a solution, but 1) It would hammer on the client machine (which might not be kind for the user) and 2) you would loose any advantage of using QuerySets and DataFrames as data structures.
Meaby i have missed out, but i can't find the order attribute
i guess will be better if the columns supports admin_order_field in costume columns method
The text was updated successfully, but these errors were encountered: