Aspnetpager True and False page comparison example

learn from the beginning BS It's been a while. the design of BS is the design of the Web page, which includes data extracted from the database and displayed on the page. Previously in CS , it was displayed using a table control such as the GridView, because the data was small and the right side had a scroll wheel. So I never thought about paging the data. So this is a big mistake. It's not too late to react. Next, let's touch the paging.

Disadvantages of Not paging:

the query operations on big data.

1 , the amount of data is too large, the form loading time is too slow

2 , the amount of data displayed is too large and the user looks uncomfortable.

Two ways to split pages:

False paging:

In the execution of the query, all the data are queried, and then jump to the page when You do not need to query.

True paging:

When you perform a query operation, only the contents of the current page that is displayed are queried for display. After the jump page also need to query the database to fetch the corresponding data.

In the case of large data volumes, compare:

in the case of small data, because now the computer processing speed is fast enough, the use of true paging and false paging user experience is no different.

for information on how to add Aspnetpager controls, borrow the following articles:

http://blog.csdn.net/u010066934/article/details/38374111

True and false Pagination example result diagram:

Use the own GridView table to display the data. Use the Aspnetpager control for paging.

How to use Aspnetpager please flip through---。 I will not dwell on it.

HTML Main interface:

<table class= "Auto-style1" > <tr> <td>                        <webdiyer:aspnetpager id= "Anptop" runat= "Server" pagesize= "5" onpagechanged= "anp_pagechanged" >                </webdiyer:AspNetPager> </td> </tr> <tr> <td class= "Auto-style2" > <asp:gridview id= "GridView1" ru                nat= "Server" > </asp:GridView> </td> </tr> <tr> <td> <webdiyer:aspnetpager id= "Anpbottom" runat = "Server" clonefrom= "Anptop" cssclass= "ANP" onpagechanged= "anp_pagechanged" pagesize= "5" > </w ebdiyer:aspnetpager> </td> </tr> </table> 

First, set a paging control at the header, and then copy the above control to the bottom, so that it achieves the effect of synchronization.

In order to compare the true and false pagination, first look at the implementation of false paging:

Using system;using system.collections.generic;using system.linq;using system.web;using System.Web.UI;using System.web.ui.webcontrols;using system.data;using system.data.sqlclient;namespace news{public partial class JiaFenYe : System.Web.UI.Page {DataView dv = new DataView (DB).        GetSource ());            protected void Page_Load (object sender, EventArgs e) {//anptop.recordcount = Db.count (); Save the total number of records for the data into the paging control//gridview1.datasource = DB.   GetSource (1, 5);            The default selection of 5 records//gridview1.databind ();            Anptop.recordcount = Db.count (); Saves the total number of records in the data to the paging control in DV.             RowFilter = "id<=5";            The default first page shows 5 records gridview1.datasource = DV;           Gridview1.databind (); Bound view} protected void Anp_pagechanged (object sender, EventArgs e) {//response.write ("Start            Page number: "+ Anptop.startrecordindex +" <br> End page: "+ anptop.endrecordindex); int StartIndex = Anptop.startrecordindex;           In fact, the record number int endIndex = Anptop.endrecordindex; Stop record number//dataview DV = new DataView (DB).            GetSource ()); Dv.      RowFilter = "id >=" + startIndex + "and id<=" + endIndex;            Query the record within the specified interval Gridview1.datasource = DV;           Gridview1.databind (); Bound View}}}

In contrast, true paging is implemented:

Using system;using system.collections.generic;using system.linq;using system.web;using System.Web.UI;using System.web.ui.webcontrols;namespace news{public    partial class WebForm1:System.Web.UI.Page    {        protected void Anp_pagechanged (object sender, EventArgs e)        {            //response.write ("Start Page:" + Anptop.startrecordindex + "< Br> End Page: "+ anptop.endrecordindex);            int startIndex = Anptop.startrecordindex;       Number of start records of data            int endIndex = Anptop.endrecordindex;           Number of cutoff records for data            Gridview1.datasource = DB. GetSource (startindex,endindex);   Displays the data in the current interval            gridview1.databind ();        }        protected void Page_Load (object sender, EventArgs e)        {            anptop.recordcount = Db.count ();            Save the total number of records for the data into the paging control            Gridview1.datasource = DB. GetSource (1,5);   Default selection 5 records            gridview1.databind ();}}}    

by comparing the above experimental results, it is not obvious that the measured data is too small. However, through the code implementation process, it can be seen that in the premise of big data, false paging loading is a big problem. Of course, the two types of paging have their own characteristics, can be based on the actual needs to choose.

If you need to see the source code, please download it yourself:

http://download.csdn.net/detail/zc474235918/7734743