Comments on: Thinking about the pagination feature

By: Fabricio Sodano

Fabricio Sodano — Tue, 17 Mar 2009 15:48:28 +0000

All right! I’ll try that.

Thanks a lot!

By: cakebaker

cakebaker — Tue, 17 Mar 2009 15:47:07 +0000

@Fabricio: Thanks for your comment!

The only solution I see at the moment is to copy the paginate() method from the Controller class and to add this method to your own controller. Then you can apply your change there.

And regarding side effects, you could run the test case for the Controller class, and see whether it will fail ;-)

Hope that helps!

By: Fabricio Sodano

Fabricio Sodano — Mon, 16 Mar 2009 17:49:57 +0000

Hello…

This is an old topic, I know… but as today there was no way to fix this (The DISCTINCT not being applied to the count) however, i’ve found that in the controller.php file, the paginate method has this line to fetch the count for the pagination:

$count = $object->find(‘count’, array_merge($parameters, $extra));

However, when you go and look into the paginate method, the 2nd param is the “fields” array, so… I’ve changed the previous line to:

$count = $object->find(‘count’, $fields);

And now it works fully. However, I’m pretty sure it will have side effects, but I haven’t seen any yet :)

My question is: Is there another way to implement this solution *specifically* for this particular case instead of the full app?

Cheers & Thanks!

By: Pixelastic

Pixelastic — Tue, 19 Aug 2008 15:09:47 +0000

Hmm, you’re right, maybe I should limit myself only to the model(s) who actually need it.

By: cakebaker

cakebaker — Tue, 19 Aug 2008 06:10:17 +0000

@Pixelastic: Do you know YAGNI? ;-)

By: Pixelastic

Pixelastic — Mon, 18 Aug 2008 16:17:42 +0000

I could have limited myself to adding paginate and paginateCount to the only model that actually needed such a treatment, but I think multiple custom pagination could be useful in the future for other models.

By: cakebaker

cakebaker — Mon, 18 Aug 2008 16:09:13 +0000

@Pixelastic: I’m glad you found a solution. Personally, I wouldn’t add paginate() and paginateCount() to the AppModel if it is not really necessary, but else your approach looks fine.

By: Pixelastic

Pixelastic — Mon, 18 Aug 2008 08:59:17 +0000

@myself : I have found a way, I just have to :

1/ create a Model::paginateIndex and Model::paginateCountIndex methods for paginating my index page. (and multiple other methods for each special pagination I will need)

2/ Overriding the AppModel::paginate and AppModel::paginateCount methods with my own, checking for the $conditions params and if a string (eg. ‘index’) returning the corresponding method in the model ( $paginateFunction = $paginate”.Inflector::camelize($conditions); ) and returning $this->{$paginateFunction}([...]);
(same goes for paginateCount)

3/ Calling my paginate action in my controller like
$this->paginate = array(‘conditions’ => ‘index’);
$itemList = $this->paginate();

By: Pixelastic

Pixelastic — Sun, 17 Aug 2008 23:35:44 +0000

As noted before, first comment : “Also, your point about the paginate/paginateCount methods is pretty much moot, since you can define as many alternative types of finders for the find() method as you want, and/or pass in custom flags in the options array.”

Can please somebody expand on that ? I’m stuck on how to define different pagination rules for one same controller.
I need a special paginate for the admin panel and another for the public page (the latter is quite complicated and needs a very special treatment), but I would like to find a more generic way to define multiple pagination rules for the same controller.

By: cakebaker

cakebaker — Thu, 31 Jul 2008 15:36:37 +0000

@rick: You could implement paginate() and paginateCount() in your model for this purpose. But I’m not sure whether this is the best solution, maybe someone in the CakePHP Google Group has a better idea.

Hope that helps!