for panel UI datatables such as callhistory, automatic rowcount clipping comes into effect, to prevent pageloads taking minutes with large calllists. the clipping also requires special handling of any queries with an OR clause, which we explicitly expressed as compound queries (set operations eg. UNION) meanwhile (fortunately!). this allows to improve the query speed in such cases, by injecting the filter condition to each subset query. when introducing this technique, it was clear to sacrifice ordering of the result, since sorting is pointless when merging clipped subsets with UNION. allthoug the UI provides a subtle hint whenever clipping occurs, this is not intuitive to users (what else). this is an attempt to improve the situation by applying the order clauses to the subsets. this way eg. the initial sorting (timestamp descending) of the callhistory datatable should show the recent items properly and effectively clip away the older entries. Change-Id: Ia249e96ac4330cfcdb4905ce2cd0b925aace80f4changes/12/31112/8
parent
856cc68e88
commit
0c93d71e90
Loading…
Reference in new issue