projects / dbsrgits/DBIx-Class.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 32cff86)
Revert incorrect assumption about non-functional cached pagers 65245220
authorPeter Rabbitson <ribasushi@cpan.org>
Sat, 30 Apr 2011 00:43:30 +0000 (02:43 +0200)
committerPeter Rabbitson <ribasushi@cpan.org>
Mon, 2 May 2011 10:59:42 +0000 (12:59 +0200)
commit74719352f7e25d81f00de886daa77094ce3289f8
tree6f7bec4737ddc8a46984ff8490a69885a02a6f79tree | snapshot
parent32cff863db45d7f965a7587929a5db56dfb4ef75commit | diff
Revert incorrect assumption about non-functional cached pagers 65245220

While on the surface it seems logical that a cached resultset is inherently
non-pageable, one has to remember that search chaining with different
arguments (i.e. different offset) fires a new query, not subject to the
existing resultset cache.
Changes diff | blob | blame | history
lib/DBIx/Class/ResultSet.pm diff | blob | blame | history
t/67pager.t diff | blob | blame | history
The Perl ORM (dbsrgits@git.shadowcat.co.uk:DBIx-Class.git)