Module: WillPaginate::Finder::ClassMethods
- Defined in:
- lib/will_paginate/finder.rb
Overview
Paginating finders for ActiveRecord models
WillPaginate adds paginate
, per_page
and other methods to ActiveRecord::Base class methods and associations. It also hooks into method_missing
to intercept pagination calls to dynamic finders such as paginate_by_user_id
and translate them to ordinary finders (find_all_by_user_id
in this case).
In short, paginating finders are equivalent to ActiveRecord finders; the only difference is that we start with “paginate” instead of “find” and that :page
is required parameter:
@posts = Post.paginate :all, :page => params[:page], :order => 'created_at DESC'
In paginating finders, “all” is implicit. There is no sense in paginating a single record, right? So, you can drop the :all
argument:
Post.paginate(...) => Post.find :all
Post.paginate_all_by_something => Post.find_all_by_something
Post.paginate_by_something => Post.find_all_by_something
The importance of the :order
parameter
In ActiveRecord finders, :order
parameter specifies columns for the ORDER BY
clause in SQL. It is important to have it, since pagination only makes sense with ordered sets. Without the ORDER BY
clause, databases aren’t required to do consistent ordering when performing SELECT
queries; this is especially true for PostgreSQL.
Therefore, make sure you are doing ordering on a column that makes the most sense in the current context. Make that obvious to the user, also. For perfomance reasons you will also want to add an index to that column.
Instance Method Summary collapse
-
#paginate(*args, &block) ⇒ Object
This is the main paginating finder.
-
#paginate_by_sql(sql, options) ⇒ Object
Wraps
find_by_sql
by simply adding LIMIT and OFFSET to your SQL string based on the params otherwise used by paginating finds:page
andper_page
. -
#paginated_each(options = {}, &block) ⇒ Object
Iterates through all records by loading one page at a time.
-
#respond_to?(method, include_priv = false) ⇒ Boolean
:nodoc:.
Instance Method Details
#paginate(*args, &block) ⇒ Object
This is the main paginating finder.
Special parameters for paginating finders
-
:page
– REQUIRED, but defaults to 1 if false or nil -
:per_page
– defaults toCurrentModel.per_page
(which is 30 if not overridden) -
:total_entries
– use only if you manually count total entries -
:count
– additional options that are passed on tocount
-
:finder
– name of the ActiveRecord finder used (default: “find”)
All other options (conditions
, order
, …) are forwarded to find
and count
calls.
88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 |
# File 'lib/will_paginate/finder.rb', line 88 def paginate(*args, &block) = args.pop page, per_page, total_entries = () finder = ([:finder] || 'find').to_s if finder == 'find' # an array of IDs may have been given: total_entries ||= (Array === args.first and args.first.size) # :all is implicit args.unshift(:all) if args.empty? end WillPaginate::Collection.create(page, per_page, total_entries) do |pager| = .except :page, :per_page, :total_entries, :finder = .except(:count).update(:offset => pager.offset, :limit => pager.per_page) args << # @options_from_last_find = nil pager.replace send(finder, *args, &block) # magic counting for user convenience: pager.total_entries = wp_count(, args, finder) unless pager.total_entries end end |
#paginate_by_sql(sql, options) ⇒ Object
Wraps find_by_sql
by simply adding LIMIT and OFFSET to your SQL string based on the params otherwise used by paginating finds: page
and per_page
.
Example:
@developers = Developer.paginate_by_sql ['select * from developers where salary > ?', 80000],
:page => params[:page], :per_page => 3
A query for counting rows will automatically be generated if you don’t supply :total_entries
. If you experience problems with this generated SQL, you might want to perform the count manually in your application.
155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 |
# File 'lib/will_paginate/finder.rb', line 155 def paginate_by_sql(sql, ) WillPaginate::Collection.create(*()) do |pager| query = sanitize_sql(sql.dup) original_query = query.dup # add limit, offset add_limit! query, :offset => pager.offset, :limit => pager.per_page # perfom the find pager.replace find_by_sql(query) unless pager.total_entries count_query = original_query.sub /\bORDER\s+BY\s+[\w`,\s]+$/mi, '' count_query = "SELECT COUNT(*) FROM (#{count_query})" unless ['oracle', 'oci'].include?(self.connection.adapter_name.downcase) count_query << ' AS count_table' end # perform the count query pager.total_entries = count_by_sql(count_query) end end end |
#paginated_each(options = {}, &block) ⇒ Object
Iterates through all records by loading one page at a time. This is useful for migrations or any other use case where you don’t want to load all the records in memory at once.
It uses paginate
internally; therefore it accepts all of its options. You can specify a starting page with :page
(default is 1). Default :order
is "id"
, override if necessary.
See Faking Cursors in ActiveRecord where Jamis Buck describes this and a more efficient way for MySQL.
123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 |
# File 'lib/will_paginate/finder.rb', line 123 def paginated_each( = {}, &block) = { :order => 'id', :page => 1 }.merge [:page] = [:page].to_i [:total_entries] = 0 # skip the individual count queries total = 0 begin collection = paginate() with_exclusive_scope(:find => {}) do # using exclusive scope so that the block is yielded in scope-free context total += collection.each(&block).size end [:page] += 1 end until collection.size < collection.per_page total end |
#respond_to?(method, include_priv = false) ⇒ Boolean
:nodoc:
177 178 179 180 181 182 183 184 |
# File 'lib/will_paginate/finder.rb', line 177 def respond_to?(method, include_priv = false) #:nodoc: case method.to_sym when :paginate, :paginate_by_sql true else super(method.to_s.sub(/^paginate/, 'find'), include_priv) end end |