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
Environment
v3.1
Attachments
2
Activity
Show:
Heng Sin Low May 9, 2020 at 11:57 AM
Not reproduce-able on current version (7.1 and 7.1z)
Hiep Lq February 15, 2017 at 6:47 AM
I think "Tested By" for filter after you verify a patch.
Hiep Lq February 15, 2017 at 6:45 AM
i think peer review is when you have a patch and make sure it can integrate into core not idea or other things
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