You can achieve the desired result by requesting a list of distinct ids instead of a list of distinct hydrated objects. Simply add this to your criteria: criteria.setProjection(Projections.distinct(Projections.property(“id”))); Now you’ll get the correct number of results according to your row-based limiting. The reason this works is because the projection will perform the distinctness check as … Read more
Save your sorting order in a ViewState. private const string ASCENDING = ” ASC”; private const string DESCENDING = ” DESC”; public SortDirection GridViewSortDirection { get { if (ViewState[“sortDirection”] == null) ViewState[“sortDirection”] = SortDirection.Ascending; return (SortDirection) ViewState[“sortDirection”]; } set { ViewState[“sortDirection”] = value; } } protected void GridView_Sorting(object sender, GridViewSortEventArgs e) { string sortExpression = … Read more
First of all I want repeat that I don’t recommend you to use local sorting and the server side paging. I find that the user can wrong interpret the result of sorting. Nevertheless, if your customer agree with restriction which have the combination of local sorting and the server side paging and if you really … Read more
Using skip+limit is not a good way to do paging when performance is an issue, or with large collections; it will get slower and slower as you increase the page number. Using skip requires the server to walk though all the documents (or index values) from 0 to the offset (skip) value. It is much … Read more
You’re looking for the Skip and Take extension methods. Skip moves past the first N elements in the result, returning the remainder; Take returns the first N elements in the result, dropping any remaining elements. See MSDN for more information on how to use these methods: http://msdn.microsoft.com/en-us/library/bb386988.aspx Assuming you are already taking into account that … Read more