on field with date+time, when field is not mandatory sorting has wrong behaviour (excl. eg. created, updated). in case of lot null sorting is unusable, because split data set am, pm, makes unreadable for user.
example - wrong behaviour (also attached an example from m_inout shipdate field) 01/27/2017 6:36:51 AM 01/27/2017 11:28:58 AM 01/27/2017 null 01/27/2017 1:24:25 PM
instead (asc) 01/27/2017 6:36:51 AM 01/27/2017 11:28:58 AM 01/27/2017 1:24:25 PM 01/27/2017 null
instead (desc) 01/27/2017 1:24:25 PM 01/27/2017 11:28:58 AM 01/27/2017 6:36:51 AM 01/27/2017 null
on field with date+time, when field is not mandatory sorting has wrong behaviour (excl. eg. created, updated). in case of lot null sorting is unusable, because split data set am, pm, makes unreadable for user.
example - wrong behaviour (also attached an example from m_inout shipdate field)
01/27/2017 6:36:51 AM
01/27/2017 11:28:58 AM
01/27/2017 null
01/27/2017 1:24:25 PM
instead (asc)
01/27/2017 6:36:51 AM
01/27/2017 11:28:58 AM
01/27/2017 1:24:25 PM
01/27/2017 null
instead (desc)
01/27/2017 1:24:25 PM
01/27/2017 11:28:58 AM
01/27/2017 6:36:51 AM
01/27/2017 null