Timeline for Display large amount of data to client through pagination
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 31, 2013 at 16:52 | answer | added | akp | timeline score: 0 | |
| Oct 30, 2013 at 12:29 | answer | added | Mohsen Heydari | timeline score: 1 | |
| Oct 30, 2013 at 12:11 | answer | added | Neil | timeline score: 1 | |
| Oct 30, 2013 at 11:36 | comment | added | ebram khalil | @MohsenHeydari sql server | |
| Oct 30, 2013 at 11:31 | answer | added | Julia Hayward | timeline score: 5 | |
| Oct 30, 2013 at 11:29 | comment | added | Mohsen Heydari | What database you are using? | |
| Oct 30, 2013 at 11:17 | comment | added | Ozair Kafray | Can't answer in detail but 1 is not a good idea. 2 is the way to start and then move towards what is suggested by @Mike52 | |
| Oct 30, 2013 at 11:12 | comment | added | thorsten müller | I am not really into the ASP.NET area, so wouldn't knw which tutorials there are. In general adding paging to a web site isn't that difficult and there exist many plugins to help with it (eg adding those typical prev, 1,2,3...21,22, next structure of links). It doesn't take much more than to count the number of rows, calculate the actual page offset and page_size and query with LIMIT. | |
| Oct 30, 2013 at 11:04 | comment | added | ebram khalil | @thorstenmüller can you guide me with simple tutorials? | |
| Oct 30, 2013 at 11:01 | comment | added | thorsten müller | Second approach would be the more common one in most use cases (there may be project specific exceptions of course, for example depending on database load). Chances are your database caches those requests anyway. (Otherwise some performance testing may be appropriate in this situation) | |
| Oct 30, 2013 at 11:00 | review | First posts | |||
| Oct 30, 2013 at 12:56 | |||||
| Oct 30, 2013 at 10:54 | answer | added | Mike52 | timeline score: 2 | |
| Oct 30, 2013 at 10:43 | history | asked | ebram khalil | CC BY-SA 3.0 |