Timeline for pagination on data fetched using SQL query
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 9, 2019 at 11:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 8, 2019 at 1:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 26, 2016 at 9:43 | answer | added | Salik Asad | timeline score: 3 | |
| Jul 26, 2016 at 9:43 | comment | added | Andy Macaulay-Brook | Great - it's fine to post your own answer. Make sure you accept it too! | |
| Jul 26, 2016 at 9:42 | comment | added | Salik Asad | Thanks @AndyMacaulay-Brook for this response. There was a problem with my COUNT query which i have resolved and posted an answer for this question so that other users having this type of query can get help from here. | |
| Jul 26, 2016 at 9:36 | comment | added | Andy Macaulay-Brook | You're fetching custom records and not Posts in the WP sense of the word. Do you really need to use a separate table for this data, or would you be better off storing it as a custom post type? If you can store it as custom posts, then you get the benefit of WP's API including pagination of lists of posts. | |
| Jul 26, 2016 at 6:57 | history | edited | Salik Asad | CC BY-SA 3.0 |
added 9 characters in body
|
| Jul 26, 2016 at 6:49 | history | edited | Salik Asad | CC BY-SA 3.0 |
added 932 characters in body
|
| Jul 26, 2016 at 6:33 | history | asked | Salik Asad | CC BY-SA 3.0 |