Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Order attribute is missing #9

Open
SoulRaven opened this issue Oct 19, 2016 · 2 comments
Open

Order attribute is missing #9

SoulRaven opened this issue Oct 19, 2016 · 2 comments

Comments

@SoulRaven
Copy link

SoulRaven commented Oct 19, 2016

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

@oberix
Copy link
Member

oberix commented Oct 20, 2016

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.

@SoulRaven
Copy link
Author

i understand, the problem is that when are used costumes fields with methods, the order feature is not there anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants