Initial sorting equals sortColumn

[ismooth]

After a user has changed sorting order of DataObjects in the list, and when drag&drop is disabled, sorting is made by $default_sort from that DataObjects property or default set by SS. This results in different sorting when checkbox is enabled or disabled what confuses users. This change always sorts the list by $sortColumn, so that user always sees same sorting.

[UndefinedOffset]

Thanks, I've never noticed this because I always set the default sort to be the sort column. Out of curiosity what was the use case for having the default_sort different from the sort column?

[ismooth]

Hi,

I have Keyword (DataObject) which is many_many related to Articles. When I
create new Keyword I first check it's existence using
Keyword::get()->filter(...)->first(). If I set $default_sort of Keyword to
SortOrder (which actually only exists in the relation, but not on
DataObject itself) and try to do the lookup, I get SQL error cause SS tries
to do the sorting according to SortOrder column which doesn't exist in
Keyword table. Therefore I need different $default_sort from 'SortOrder'.

Cheers,
Igor

On Fri, Oct 3, 2014 at 4:23 PM, Ed Chipman [email protected] wrote:

Thanks, I've never noticed this because I always set the default sort to
be the sort column. Out of curiosity what was the use case for having the
default_sort different from the sort column?

—
Reply to this email directly or view it on GitHub
#61 (comment)
.

[UndefinedOffset]

Ah cool that makes allot of sense, I was just wondering :)