StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8204464
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-11-20T20:27:45.023
FavoriteCount
0
LastActivityDate
2011-11-20T20:38:05.860
LastEditDate
2011-11-20T20:38:05.860
LastEditorUserId
62082
OwnerUserId
62082
ParentId
8204052
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
It looks like will_paginate imposes its own <code>limit</code> clause on your relation in order to do the paging. After some experimentation, the easiest way I could find to do this is to do eager-loading of the result set and use the functionality contained in <a href="https://github.com/mislav/will_paginate/blob/master/lib/will_paginate/array.rb#files" rel="noreferrer">the array extensions</a> to do the actual pagination. Here's a quick example; note that you have to require <code>will_paginate/array</code>; you may wish to do this in an initializer or somewhere else. Note that it does monkey-patch <code>Array</code> to have the <code>paginate</code> method. <pre><code>require 'will_paginate/array' class ArticlesController < ApplicationController def index @articles = Article.published.limit(20).all # call `all` to eager load @articles = @articles.paginate(:page => params[:page], :per_page => 10) end end </code></pre> [Update] Another option is to pass in the <code>total_entires</code> option to will_paginate based on the result set size. <pre><code>class ArticlesController < ApplicationController def index @articles = Article.published.limit(20) @articles = @articles.paginate(:page => params[:page], :per_page => 10, :total_entries => @articles.count) end end </code></pre> You can't pass in 20 as you can't guarantee that a full 20 results will be returned; by passing in the <code>count</code> attribute, you can ensure that the pagination will be correct.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POrails 3, will_paginate over existing limited active record result
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USMichelle Tilley
UserOwnerUserId
1. USMichelle Tilley
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POrails 3, will_paginate over existing limited active record result
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COty brandon works like a charm, that was what i was searching for
 singulars
 PostPostId
 PO
 UserUserId
 UShereandnow78

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.