The content of an article is displayed by page. If the content of an article is too long, we will consider pagination of the content. For this requirement, we must first consider a one-to-many relationship from the perspective of database design. Therefore, you need to design two tables to store the article information. The first one is basic, such as the title, abstract, author, and other fields. The other table stores the content of the article. It is a field associated with the primary key of the first table, the relationship between the foreign key and the primary key, and the other field is the storage content.
The content of the article is divided into several pages, which is a matter of the user. If it is a short text, the user will upload it once. If the content is too long, you can upload it several times considering the need for paging.
Pagination: when there is only one page (only one record is required here), the pagination toolbar is not displayed when the webpage is displayed. If it is more than one record, it is displayed on the toolbar.
In the following animation demonstration, the content of Insus. NET was initially edited in the article. It does not include the normal display of the article on the webpage. First, add the content of the first table (this step is omitted in the animation). At the beginning, the animation has been added.
You can add article content consecutively without adding any paging flag. Because it is a record every time it is added and uploaded.
Of course, the content of the added article is more comprehensive. After the content is added, it can be immediately displayed below, so that you do not have to go back to the previous page to see the added content. You can also insert the content of an article to any page or sort the content pages of the uploaded article.
In fact, this is only a form. All the functional technologies mentioned have solutions.
In addition, Insus. NET implementation in paging instances, you can refer to the http://www.cnblogs.com/insus/tag/Paging/