StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8223669
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2011-11-22T08:04:36.557
FavoriteCount
0
LastActivityDate
2011-11-23T00:10:38.163
LastEditDate
2011-11-23T00:10:38.163
LastEditorUserId
206881
OwnerUserId
206881
ParentId
8223341
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
It sounds like an approach issue. Why are you using POST data to filter your data? The pagination library builds a query string to determine the offset of your database query results. Why can't you use $_GET instead of $_POST? I suppose it would be possible to set your pagination config 'base_url' to this: <pre><code>$this->load->helper('url'); $this->load->library('pagination'); $config['base_url'] = current_url().'?'.http_build_query($_POST); $config['total_rows'] = 200; $config['per_page'] = 20; $this->pagination->initialize($config); echo $this->pagination->create_links(); </code></pre> And then in your controller, use $this->input->get_post(), rather than $this->input->post(). Be careful here--it's rarely safe to pass the full post data directly into a model for processing. It would be better to use CI's input class to prevent XSS attacks... UPDATE: To use CI's input class, rather than $_POST or $_GET directly, I usually keep my form data in a "namespace" of sorts, i.e.: <pre><code><input type="text" name="search[criteria1]" /> <input type="text" name="search[criteria2]" /> <input type="text" name="search[criteria3]" /> </code></pre> Then, in your controller: <pre><code>... public function some_resource() { $this->load->model('Some_model'); $search_criteria = $this->input->get_post('search'); if ($search_criteria) { // make sure here to remove any unsupported criteria // (or in the model is usually a bit more modular, but // it depends on how strictly you follow MVC) $results = $this->Some_model->search($search_criteria); } else { // If no search criteria were given, return unfiltered results $results = $this->Some_model->get_all(); } $this->load->view('some_view', array( 'results' => $results, 'pagination_base' => current_url().'?'.http_build_query($search_criteria) )); } ... </code></pre> Because I specified $this->input->get_post(), it will first check for a query string parameter; if it doesn't exist, it falls back to post data. This will allow you to use POST in your form, but still pass in the same data through the query string with the pagination class. However, really the form should be using the GET method, as you're sending these parameters as a query, and not to send something to the server. Just my $.02 on that detail.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POcodeigniter pagination with selected records
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USlandons
UserOwnerUserId
1. USlandons
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POcodeigniter pagination with selected records
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.