djmaze-will_paginate 2.3.13

Sign up to get free protection for your applications and to get access to all the features.
@@ -0,0 +1,139 @@
1
+ = 2.3.12, released 2009-12-01
2
+
3
+ * make view helpers "HTML safe" for Rails 2.3.5 with rails_xss plugin
4
+
5
+ = 2.3.11, released 2009-06-02
6
+
7
+ * fix `enable_actionpack`
8
+
9
+ = 2.3.10, released 2009-05-21
10
+
11
+ * count_by_sql: don't use table alias with any adapters starting with "oracle"
12
+ * Add back "AS count_table" alias to `paginate_by_sql` counter SQL
13
+
14
+ = 2.3.9, released 2009-05-29
15
+
16
+ * remove "AS count_table" alias from `paginate_by_sql` counter SQL
17
+ * Rails 2.3.2 compat: monkeypatch Rails issue #2189 (count breaks has_many :through)
18
+ * fix generation of page URLs that contain the "@" character
19
+ * check for method existance in a ruby 1.8- and 1.9-compatible way
20
+ * load will_paginate view helpers even if ActiveRecord is not loaded
21
+
22
+ == 2.3.8, released 2009-03-09
23
+
24
+ * Rails 2.3 compat: query parameter parsing with Rack
25
+
26
+ == 2.3.7, released 2009-02-09
27
+
28
+ * Removed all unnecessary &block variables since they cause serious memory damage and lots of subsequent gc runs.
29
+
30
+ == 2.3.6, released 2008-10-26
31
+
32
+ * Rails 2.2 fix: stop using `extract_attribute_names_from_match` inernal AR method, it no longer exists
33
+
34
+ == 2.3.5, released 2008-10-07
35
+
36
+ * update the backported named_scope implementation for Rails versions older than 2.1
37
+ * break out of scope of paginated_each() yielded block when used on named scopes
38
+ * fix paginate(:from)
39
+
40
+ == 2.3.4, released 2008-09-16
41
+
42
+ * Removed gem dependency to Active Support (causes trouble with vendored rails).
43
+ * Rails 2.1: fix a failing test and a deprecation warning.
44
+ * Cope with scoped :select when counting.
45
+
46
+ == 2.3.3, released 2008-08-29
47
+
48
+ * Ensure that paginate_by_sql doesn't change the original SQL query.
49
+ * RDoc love (now live at http://gitrdoc.com/mislav/will_paginate/tree/master)
50
+ * Rename :prev_label to :previous_label for consistency. old name still functions but is deprecated
51
+ * ActiveRecord 2.1: Remove :include option from count_all query when it's possible.
52
+
53
+ == 2.3.2, released 2008-05-16
54
+
55
+ * Fixed LinkRenderer#stringified_merge by removing "return" from iterator block
56
+ * Ensure that 'href' values in pagination links are escaped URLs
57
+
58
+ == 2.3.1, released 2008-05-04
59
+
60
+ * Fixed page numbers not showing with custom routes and implicit first page
61
+ * Try to use Hanna for documentation (falls back to default RDoc template if not)
62
+
63
+ == 2.3.0, released 2008-04-29
64
+
65
+ * Changed LinkRenderer to receive collection, options and reference to view template NOT in
66
+ constructor, but with the #prepare method. This is a step towards supporting passing of
67
+ LinkRenderer (or subclass) instances that may be preconfigured in some way
68
+ * LinkRenderer now has #page_link and #page_span methods for easier customization of output in
69
+ subclasses
70
+ * Changed page_entries_info() method to adjust its output according to humanized class name of
71
+ collection items. Override this with :entry_name parameter (singular).
72
+
73
+ page_entries_info(@posts)
74
+ #-> "Displaying all 12 posts"
75
+ page_entries_info(@posts, :entry_name => 'item')
76
+ #-> "Displaying all 12 items"
77
+
78
+ == 2.2.3, released 2008-04-26
79
+
80
+ * will_paginate gem is no longer published on RubyForge, but on
81
+ gems.github.com:
82
+
83
+ gem sources -a http://gems.github.com/ (you only need to do this once)
84
+ gem install mislav-will_paginate
85
+
86
+ * extract reusable pagination testing stuff into WillPaginate::View
87
+ * rethink the page URL construction mechanizm to be more bulletproof when
88
+ combined with custom routing for page parameter
89
+ * test that anchor parameter can be used in pagination links
90
+
91
+ == 2.2.2, released 2008-04-21
92
+
93
+ * Add support for page parameter in custom routes like "/foo/page/2"
94
+ * Change output of "page_entries_info" on single-page collection and erraneous
95
+ output with empty collection as reported by Tim Chater
96
+
97
+ == 2.2.1, released 2008-04-08
98
+
99
+ * take less risky path when monkeypatching named_scope; fix that it no longer
100
+ requires ActiveRecord::VERSION
101
+ * use strings in "respond_to?" calls to work around a bug in acts_as_ferret
102
+ stable (ugh)
103
+ * add rake release task
104
+
105
+
106
+ == 2.2.0, released 2008-04-07
107
+
108
+ === API changes
109
+ * Rename WillPaginate::Collection#page_count to "total_pages" for consistency.
110
+ If you implemented this interface, change your implementation accordingly.
111
+ * Remove old, deprecated style of calling Array#paginate as "paginate(page,
112
+ per_page)". If you want to specify :page, :per_page or :total_entries, use a
113
+ parameter hash.
114
+ * Rename LinkRenderer#url_options to "url_for" and drastically optimize it
115
+
116
+ === View changes
117
+ * Added "prev_page" and "next_page" CSS classes on previous/next page buttons
118
+ * Add examples of pagination links styling in "examples/index.html"
119
+ * Change gap in pagination links from "..." to
120
+ "<span class="gap">&hellip;</span>".
121
+ * Add "paginated_section", a block helper that renders pagination both above and
122
+ below content in the block
123
+ * Add rel="prev|next|start" to page links
124
+
125
+ === Other
126
+
127
+ * Add ability to opt-in for Rails 2.1 feature "named_scope" by calling
128
+ WillPaginate.enable_named_scope (tested in Rails 1.2.6 and 2.0.2)
129
+ * Support complex page parameters like "developers[page]"
130
+ * Move Array#paginate definition to will_paginate/array.rb. You can now easily
131
+ use pagination on arrays outside of Rails:
132
+
133
+ gem 'will_paginate'
134
+ require 'will_paginate/array'
135
+
136
+ * Add "paginated_each" method for iterating through every record by loading only
137
+ one page of records at the time
138
+ * Rails 2: Rescue from WillPaginate::InvalidPage error with 404 Not Found by
139
+ default
data/LICENSE ADDED
@@ -0,0 +1,18 @@
1
+ Copyright (c) 2007 PJ Hyett and Mislav Marohnić
2
+
3
+ Permission is hereby granted, free of charge, to any person obtaining a copy of
4
+ this software and associated documentation files (the "Software"), to deal in
5
+ the Software without restriction, including without limitation the rights to
6
+ use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
7
+ the Software, and to permit persons to whom the Software is furnished to do so,
8
+ subject to the following conditions:
9
+
10
+ The above copyright notice and this permission notice shall be included in all
11
+ copies or substantial portions of the Software.
12
+
13
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
14
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
15
+ FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
16
+ COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
17
+ IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
18
+ CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
@@ -0,0 +1,107 @@
1
+ = WillPaginate
2
+
3
+ Pagination is just limiting the number of records displayed. Why should you let
4
+ it get in your way while developing, then? This plugin makes magic happen. Did
5
+ you ever want to be able to do just this on a model:
6
+
7
+ Post.paginate :page => 1, :order => 'created_at DESC'
8
+
9
+ ... and then render the page links with a single view helper? Well, now you
10
+ can.
11
+
12
+ Some resources to get you started:
13
+
14
+ * {Installation instructions}[http://github.com/mislav/will_paginate/wikis/installation]
15
+ on {the wiki}[http://github.com/mislav/will_paginate/wikis]
16
+ * Your mind reels with questions? Join our
17
+ {Google group}[http://groups.google.com/group/will_paginate].
18
+ * {How to report bugs}[http://github.com/mislav/will_paginate/wikis/report-bugs]
19
+
20
+
21
+ == Example usage
22
+
23
+ Use a paginate finder in the controller:
24
+
25
+ @posts = Post.paginate_by_board_id @board.id, :page => params[:page], :order => 'updated_at DESC'
26
+
27
+ Yeah, +paginate+ works just like +find+ -- it just doesn't fetch all the
28
+ records. Don't forget to tell it which page you want, or it will complain!
29
+ Read more on WillPaginate::Finder::ClassMethods.
30
+
31
+ Render the posts in your view like you would normally do. When you need to render
32
+ pagination, just stick this in:
33
+
34
+ <%= will_paginate @posts %>
35
+
36
+ You're done. (You can find the option list at WillPaginate::ViewHelpers.)
37
+
38
+ How does it know how much items to fetch per page? It asks your model by calling
39
+ its <tt>per_page</tt> class method. You can define it like this:
40
+
41
+ class Post < ActiveRecord::Base
42
+ cattr_reader :per_page
43
+ @@per_page = 50
44
+ end
45
+
46
+ ... or like this:
47
+
48
+ class Post < ActiveRecord::Base
49
+ def self.per_page
50
+ 50
51
+ end
52
+ end
53
+
54
+ ... or don't worry about it at all. WillPaginate defines it to be <b>30</b> by default.
55
+ But you can always specify the count explicitly when calling +paginate+:
56
+
57
+ @posts = Post.paginate :page => params[:page], :per_page => 50
58
+
59
+ The +paginate+ finder wraps the original finder and returns your resultset that now has
60
+ some new properties. You can use the collection as you would with any ActiveRecord
61
+ resultset. WillPaginate view helpers also need that object to be able to render pagination:
62
+
63
+ <ol>
64
+ <% for post in @posts -%>
65
+ <li>Render `post` in some nice way.</li>
66
+ <% end -%>
67
+ </ol>
68
+
69
+ <p>Now let's render us some pagination!</p>
70
+ <%= will_paginate @posts %>
71
+
72
+ More detailed documentation:
73
+
74
+ * WillPaginate::Finder::ClassMethods for pagination on your models;
75
+ * WillPaginate::ViewHelpers for your views.
76
+
77
+
78
+ == Authors and credits
79
+
80
+ Authors:: Mislav Marohnić, PJ Hyett
81
+ Original announcement:: http://errtheblog.com/post/929
82
+ Original PHP source:: http://www.strangerstudios.com/sandbox/pagination/diggstyle.php
83
+
84
+ All these people helped making will_paginate what it is now with their code
85
+ contributions or just simply awesome ideas:
86
+
87
+ Chris Wanstrath, Dr. Nic Williams, K. Adam Christensen, Mike Garey, Bence
88
+ Golda, Matt Aimonetti, Charles Brian Quinn, Desi McAdam, James Coglan, Matijs
89
+ van Zuijlen, Maria, Brendan Ribera, Todd Willey, Bryan Helmkamp, Jan Berkel,
90
+ Lourens Naudé, Rick Olson, Russell Norris, Piotr Usewicz, Chris Eppstein,
91
+ Denis Barushev, Ben Pickles.
92
+
93
+
94
+ == Usable pagination in the UI
95
+
96
+ There are some CSS styles to get you started in the "examples/" directory. They
97
+ are {showcased online here}[http://mislav.uniqpath.com/will_paginate/].
98
+
99
+ More reading about pagination as design pattern:
100
+
101
+ * {Pagination 101}[http://kurafire.net/log/archive/2007/06/22/pagination-101]
102
+ * {Pagination gallery}[http://www.smashingmagazine.com/2007/11/16/pagination-gallery-examples-and-good-practices/]
103
+ * {Pagination on Yahoo Design Pattern Library}[http://developer.yahoo.com/ypatterns/parent.php?pattern=pagination]
104
+
105
+ Want to discuss, request features, ask questions? Join the
106
+ {Google group}[http://groups.google.com/group/will_paginate].
107
+
@@ -0,0 +1,53 @@
1
+ require 'rubygems'
2
+ begin
3
+ hanna_dir = '/Users/mislav/Projects/Hanna/lib'
4
+ $:.unshift hanna_dir if File.exists? hanna_dir
5
+ require 'hanna/rdoctask'
6
+ rescue LoadError
7
+ require 'rake'
8
+ require 'rake/rdoctask'
9
+ end
10
+ load 'test/tasks.rake'
11
+
12
+ desc 'Default: run unit tests.'
13
+ task :default => :test
14
+
15
+ desc 'Generate RDoc documentation for the will_paginate plugin.'
16
+ Rake::RDocTask.new(:rdoc) do |rdoc|
17
+ rdoc.rdoc_files.include('README.rdoc', 'LICENSE', 'CHANGELOG.rdoc').
18
+ include('lib/**/*.rb').
19
+ exclude('lib/will_paginate/named_scope*').
20
+ exclude('lib/will_paginate/array.rb').
21
+ exclude('lib/will_paginate/version.rb')
22
+
23
+ rdoc.main = "README.rdoc" # page to start on
24
+ rdoc.title = "will_paginate documentation"
25
+
26
+ rdoc.rdoc_dir = 'doc' # rdoc output folder
27
+ rdoc.options << '--inline-source' << '--charset=UTF-8'
28
+ rdoc.options << '--webcvs=http://github.com/mislav/will_paginate/tree/master/'
29
+ end
30
+
31
+ desc %{Update ".manifest" with the latest list of project filenames. Respect\
32
+ .gitignore by excluding everything that git ignores. Update `files` and\
33
+ `test_files` arrays in "*.gemspec" file if it's present.}
34
+ task :manifest do
35
+ list = `git ls-files --full-name --exclude=*.gemspec --exclude=.*`.chomp.split("\n")
36
+
37
+ if spec_file = Dir['*.gemspec'].first
38
+ spec = File.read spec_file
39
+ spec.gsub! /^(\s* s.(test_)?files \s* = \s* )( \[ [^\]]* \] | %w\( [^)]* \) )/mx do
40
+ assignment = $1
41
+ bunch = $2 ? list.grep(/^test\//) : list
42
+ '%s%%w(%s)' % [assignment, bunch.join(' ')]
43
+ end
44
+
45
+ File.open(spec_file, 'w') { |f| f << spec }
46
+ end
47
+ File.open('.manifest', 'w') { |f| f << list.join("\n") }
48
+ end
49
+
50
+ task :examples do
51
+ %x(haml examples/index.haml examples/index.html)
52
+ %x(sass examples/pagination.sass examples/pagination.css)
53
+ end
@@ -0,0 +1,90 @@
1
+ require 'active_support'
2
+ require 'will_paginate/core_ext'
3
+
4
+ # = You *will* paginate!
5
+ #
6
+ # First read about WillPaginate::Finder::ClassMethods, then see
7
+ # WillPaginate::ViewHelpers. The magical array you're handling in-between is
8
+ # WillPaginate::Collection.
9
+ #
10
+ # Happy paginating!
11
+ module WillPaginate
12
+ class << self
13
+ # shortcut for <tt>enable_actionpack</tt> and <tt>enable_activerecord</tt> combined
14
+ def enable
15
+ enable_actionpack
16
+ enable_activerecord
17
+ end
18
+
19
+ # hooks WillPaginate::ViewHelpers into ActionView::Base
20
+ def enable_actionpack
21
+ return if ActionView::Base.instance_methods.include_method? :will_paginate
22
+ require 'will_paginate/view_helpers'
23
+ ActionView::Base.send :include, ViewHelpers
24
+
25
+ if defined?(ActionController::Base) and ActionController::Base.respond_to? :rescue_responses
26
+ ActionController::Base.rescue_responses['WillPaginate::InvalidPage'] = :not_found
27
+ end
28
+ end
29
+
30
+ # hooks WillPaginate::Finder into ActiveRecord::Base and classes that deal
31
+ # with associations
32
+ def enable_activerecord
33
+ return if ActiveRecord::Base.respond_to? :paginate
34
+ require 'will_paginate/finder'
35
+ ActiveRecord::Base.send :include, Finder
36
+
37
+ # support pagination on associations
38
+ a = ActiveRecord::Associations
39
+ returning([ a::AssociationCollection ]) { |classes|
40
+ # detect http://dev.rubyonrails.org/changeset/9230
41
+ unless a::HasManyThroughAssociation.superclass == a::HasManyAssociation
42
+ classes << a::HasManyThroughAssociation
43
+ end
44
+ }.each do |klass|
45
+ klass.send :include, Finder::ClassMethods
46
+ klass.class_eval { alias_method_chain :method_missing, :paginate }
47
+ end
48
+
49
+ # monkeypatch Rails ticket #2189: "count breaks has_many :through"
50
+ ActiveRecord::Base.class_eval do
51
+ protected
52
+ def self.construct_count_options_from_args(*args)
53
+ result = super
54
+ result[0] = '*' if result[0].is_a?(String) and result[0] =~ /\.\*$/
55
+ result
56
+ end
57
+ end
58
+ end
59
+
60
+ # Enable named_scope, a feature of Rails 2.1, even if you have older Rails
61
+ # (tested on Rails 2.0.2 and 1.2.6).
62
+ #
63
+ # You can pass +false+ for +patch+ parameter to skip monkeypatching
64
+ # *associations*. Use this if you feel that <tt>named_scope</tt> broke
65
+ # has_many, has_many :through or has_and_belongs_to_many associations in
66
+ # your app. By passing +false+, you can still use <tt>named_scope</tt> in
67
+ # your models, but not through associations.
68
+ def enable_named_scope(patch = true)
69
+ return if defined? ActiveRecord::NamedScope
70
+ require 'will_paginate/named_scope'
71
+ require 'will_paginate/named_scope_patch' if patch
72
+
73
+ ActiveRecord::Base.send :include, WillPaginate::NamedScope
74
+ end
75
+ end
76
+
77
+ module Deprecation # :nodoc:
78
+ extend ActiveSupport::Deprecation
79
+
80
+ def self.warn(message, callstack = caller)
81
+ message = 'WillPaginate: ' + message.strip.gsub(/\s+/, ' ')
82
+ ActiveSupport::Deprecation.warn(message, callstack)
83
+ end
84
+ end
85
+ end
86
+
87
+ if defined? Rails
88
+ WillPaginate.enable_activerecord if defined? ActiveRecord
89
+ WillPaginate.enable_actionpack if defined? ActionController
90
+ end
@@ -0,0 +1,16 @@
1
+ require 'will_paginate/collection'
2
+
3
+ # http://www.desimcadam.com/archives/8
4
+ Array.class_eval do
5
+ def paginate(options = {})
6
+ raise ArgumentError, "parameter hash expected (got #{options.inspect})" unless Hash === options
7
+
8
+ WillPaginate::Collection.create(
9
+ options[:page] || 1,
10
+ options[:per_page] || 30,
11
+ options[:total_entries] || self.length
12
+ ) { |pager|
13
+ pager.replace self[pager.offset, pager.per_page].to_a
14
+ }
15
+ end
16
+ end
@@ -0,0 +1,144 @@
1
+ module WillPaginate
2
+ # = Invalid page number error
3
+ # This is an ArgumentError raised in case a page was requested that is either
4
+ # zero or negative number. You should decide how do deal with such errors in
5
+ # the controller.
6
+ #
7
+ # If you're using Rails 2, then this error will automatically get handled like
8
+ # 404 Not Found. The hook is in "will_paginate.rb":
9
+ #
10
+ # ActionController::Base.rescue_responses['WillPaginate::InvalidPage'] = :not_found
11
+ #
12
+ # If you don't like this, use your preffered method of rescuing exceptions in
13
+ # public from your controllers to handle this differently. The +rescue_from+
14
+ # method is a nice addition to Rails 2.
15
+ #
16
+ # This error is *not* raised when a page further than the last page is
17
+ # requested. Use <tt>WillPaginate::Collection#out_of_bounds?</tt> method to
18
+ # check for those cases and manually deal with them as you see fit.
19
+ class InvalidPage < ArgumentError
20
+ def initialize(page, page_num)
21
+ super "#{page.inspect} given as value, which translates to '#{page_num}' as page number"
22
+ end
23
+ end
24
+
25
+ # = The key to pagination
26
+ # Arrays returned from paginating finds are, in fact, instances of this little
27
+ # class. You may think of WillPaginate::Collection as an ordinary array with
28
+ # some extra properties. Those properties are used by view helpers to generate
29
+ # correct page links.
30
+ #
31
+ # WillPaginate::Collection also assists in rolling out your own pagination
32
+ # solutions: see +create+.
33
+ #
34
+ # If you are writing a library that provides a collection which you would like
35
+ # to conform to this API, you don't have to copy these methods over; simply
36
+ # make your plugin/gem dependant on this library and do:
37
+ #
38
+ # require 'will_paginate/collection'
39
+ # # WillPaginate::Collection is now available for use
40
+ class Collection < Array
41
+ attr_reader :current_page, :per_page, :total_entries, :total_pages
42
+
43
+ # Arguments to the constructor are the current page number, per-page limit
44
+ # and the total number of entries. The last argument is optional because it
45
+ # is best to do lazy counting; in other words, count *conditionally* after
46
+ # populating the collection using the +replace+ method.
47
+ def initialize(page, per_page, total = nil)
48
+ @current_page = page.to_i
49
+ raise InvalidPage.new(page, @current_page) if @current_page < 1
50
+ @per_page = per_page.to_i
51
+ raise ArgumentError, "`per_page` setting cannot be less than 1 (#{@per_page} given)" if @per_page < 1
52
+
53
+ self.total_entries = total if total
54
+ end
55
+
56
+ # Just like +new+, but yields the object after instantiation and returns it
57
+ # afterwards. This is very useful for manual pagination:
58
+ #
59
+ # @entries = WillPaginate::Collection.create(1, 10) do |pager|
60
+ # result = Post.find(:all, :limit => pager.per_page, :offset => pager.offset)
61
+ # # inject the result array into the paginated collection:
62
+ # pager.replace(result)
63
+ #
64
+ # unless pager.total_entries
65
+ # # the pager didn't manage to guess the total count, do it manually
66
+ # pager.total_entries = Post.count
67
+ # end
68
+ # end
69
+ #
70
+ # The possibilities with this are endless. For another example, here is how
71
+ # WillPaginate used to define pagination for Array instances:
72
+ #
73
+ # Array.class_eval do
74
+ # def paginate(page = 1, per_page = 15)
75
+ # WillPaginate::Collection.create(page, per_page, size) do |pager|
76
+ # pager.replace self[pager.offset, pager.per_page].to_a
77
+ # end
78
+ # end
79
+ # end
80
+ #
81
+ # The Array#paginate API has since then changed, but this still serves as a
82
+ # fine example of WillPaginate::Collection usage.
83
+ def self.create(page, per_page, total = nil)
84
+ pager = new(page, per_page, total)
85
+ yield pager
86
+ pager
87
+ end
88
+
89
+ # Helper method that is true when someone tries to fetch a page with a
90
+ # larger number than the last page. Can be used in combination with flashes
91
+ # and redirecting.
92
+ def out_of_bounds?
93
+ current_page > total_pages
94
+ end
95
+
96
+ # Current offset of the paginated collection. If we're on the first page,
97
+ # it is always 0. If we're on the 2nd page and there are 30 entries per page,
98
+ # the offset is 30. This property is useful if you want to render ordinals
99
+ # side by side with records in the view: simply start with offset + 1.
100
+ def offset
101
+ (current_page - 1) * per_page
102
+ end
103
+
104
+ # current_page - 1 or nil if there is no previous page
105
+ def previous_page
106
+ current_page > 1 ? (current_page - 1) : nil
107
+ end
108
+
109
+ # current_page + 1 or nil if there is no next page
110
+ def next_page
111
+ current_page < total_pages ? (current_page + 1) : nil
112
+ end
113
+
114
+ # sets the <tt>total_entries</tt> property and calculates <tt>total_pages</tt>
115
+ def total_entries=(number)
116
+ @total_entries = number.to_i
117
+ @total_pages = (@total_entries / per_page.to_f).ceil
118
+ end
119
+
120
+ # This is a magic wrapper for the original Array#replace method. It serves
121
+ # for populating the paginated collection after initialization.
122
+ #
123
+ # Why magic? Because it tries to guess the total number of entries judging
124
+ # by the size of given array. If it is shorter than +per_page+ limit, then we
125
+ # know we're on the last page. This trick is very useful for avoiding
126
+ # unnecessary hits to the database to do the counting after we fetched the
127
+ # data for the current page.
128
+ #
129
+ # However, after using +replace+ you should always test the value of
130
+ # +total_entries+ and set it to a proper value if it's +nil+. See the example
131
+ # in +create+.
132
+ def replace(array)
133
+ result = super
134
+
135
+ # The collection is shorter then page limit? Rejoice, because
136
+ # then we know that we are on the last page!
137
+ if total_entries.nil? and length < per_page and (current_page == 1 or length > 0)
138
+ self.total_entries = offset + length
139
+ end
140
+
141
+ result
142
+ end
143
+ end
144
+ end