Queries number optimalization + more #13
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I've tried to find the One Truly Ultimate django app for model sorting, but none suited me completely. Yours was closest to ideal, so I decided to patch it.
I wonder why app should perform so many queries when saving order? Why it should call
save()
on every object (and save perform typically 2 queries for model)? Why not useupdate()
instead?Second problem: I don't want order field to be directly editable in admin. It can only confuse users. Instead, they should use drag&drop in changelist to set ordering.
So my proposition: add ORDERABLE_ORDER_EDITABLE setting which control whether
sort_order
is editable (by default it is, to provide backward compatibility). Moreover, if field is not editable, order saving useupdate
optimization (maybe it can be used even in editable case, but for uneditable it's obviously safe).Second commit add translation for column header and remove sorting option. Why? Because if someone (accidentally) reverse the sorting order and then do some drag&drop, he can be surprised that the order is just reversed from what he saw. Changelist order should not be alterable.