-
It's a long time, obviously, there's something wrong with the others!
-
Let's put it simply:
1.One request at a time.
Advantages: It can ensure that the data is as up-to-date as possible.
Disadvantages: Database queries can be slow if the amount of data is very large.
2.If you do it once and call it all after that, this is a caching technique applied, which is the opposite of 1.
Pros: Reduces the number of submissions, reduces pressure on the server, Disadvantages: No guarantee that the data is up-to-date.
3.As for which is better, the first depends on the requirements of the project team, the second depends on the requirements of the nature of the project, and the third depends on your personal habits.
4.The first implementation is a more traditional implementation, as for which convenience, this is not easy to say, Originally, the first one was more convenient, but now it is AJAX, jquery plugin, and the second implementation is also convenient.
5.The data of the page is only partially updated, is it a change in the browser address or a change in the content of the page?
Not necessarily, can't be sure"Updated some of the content"..
a) In the case of a human being, the first reaction is to take advantage of the AJAX local refresh feature, which is that the address has not changed, only the content of the page has changed.
b) If your page layout is the same, such as the same top head and left menu, then only the middle content has changed, this is generally the address has changed, so that the content of the page has also changed.
The basic stuff, I guess you know, is more confused how to choose, how to use, always want to ask other people's opinions, to form their own habits, I used to be like this, and always ask, how to achieve better, the reason is that there were too few things to do at that time, do a little more, you can experience the difference, and then form your own habits.
Good luck!
-
Do the analysis first.
What data is needed for this page?
a.Total number of records.
b.**Maximum number of displays.
c.The page number that is currently displayed.
d.This page represents the data records.
Pagination implementation process.
When you jump to the current page.
a.Get the "current page", e.g. page 2, if not, it defaults to page 1.
b.Obtain the conditions for querying records (with or without them, set as appropriate) and query the database.
c.The maximum number of records displayed per page is generally the default value, such as 10, or 2 displayed in your **
Data processing. a.According to the query conditions, the total number of eligible records is counted;
b.According to the "current page + maximum number of records per page", the records are queried out (here is a paginated query).
c.Calculate the total number of pages based on Total Records + Maximum Records per Page.
Finally, the above information is returned to the page for display.
Specify the cursor parameter when rs is turned on.
sql,conn,1,1 >>>More
According to your description, this is a very special next page button, the next page link or button on the vast majority of web pages, the octopus collector can automatically identify and automatically add the next page loop, but there are very few special cases, you are this kind of, in this case, it is not difficult to deal with, but it is not possible to generate the collection process automatically, and it is necessary to drag the process slightly semi-automatically manually: I consulted the Octopus forum for specific operation methods, Here's an excerpt of the solution from the Octopus forum reply: >>>More
Open the word document, enter the page, in the start menu bar, click Show Hide marker, you can see the page break in the document, select the page break, and press the delete key to undo the pagination. >>>More
Are you using a browser? Is it a version of the browser?
If there is a problem with the structure or style of the writing, or if there is an incompatibility especially IE6, 7, 8 >>>More
Dear Kingsoft network users, hello:
You can try to reinstall the system with Kingsoft Reload Master. >>>More