Comments on: An alternative way to define custom find types

By: cakebaker

cakebaker — Wed, 26 Nov 2008 16:21:25 +0000

@Rafael: No problem, wordpress is sometimes a bit arbitrary ;-)

By: rafaelbandeira3

rafaelbandeira3 — Sun, 23 Nov 2008 17:06:21 +0000

hey Daniel, sorry for this spammy pingback, I checked the checkbox to auto pingback links, and it even pinged my own posts back… really sorry.

By: Pretty, Painless and Productive debug with DebugKit « Something on Everything

Sun, 23 Nov 2008 06:59:13 +0000

[...] a merchand a use case of the [7640] changes a real world [...]

By: rafaelbandeira3

rafaelbandeira3 — Fri, 24 Oct 2008 18:16:05 +0000

@cakebaker: I wrote about it last month, on:
http://rafaelbandeira3.wordpress.com/2008/09/11/paginating-different-find-types/

and the follow-up explaining how to enable paginateCount for it is on my drafts, waiting to be edited… but I would really think much more usable if you could write about it… you certainlly doc much better than I do.

By: cakebaker

cakebaker — Fri, 24 Oct 2008 16:26:19 +0000

@Rafael: Hm, and how do you say the pagination functionality which find type it should use? I thought it uses always find(‘all’)…

By: rafaelbandeira3

rafaelbandeira3 — Thu, 23 Oct 2008 16:24:52 +0000

@cakebaker : so instead of using a two-state method, you endup with a second method dealing with it. Well I think it’s a matter of use case and then taste – because with 10 to 15 find methods generating different and dynamic reports, if I would implement a call for each on my paginate(), I would end in a messy trouble. btw, thanks for the thread

By: cakebaker

cakebaker — Thu, 23 Oct 2008 16:18:47 +0000

@Rafael: By implementing the paginate() method in my model.

By: rafaelbandeira3

rafaelbandeira3 — Wed, 22 Oct 2008 11:56:43 +0000

@cakebaker: and how do you manage pagination then? – ok, a findRecent wouldn’t really need pagination, but for a report for example.

By: cakebaker

cakebaker — Tue, 21 Oct 2008 16:55:12 +0000

@Rafael: No, I haven’t used it in practice yet. And I’m not sure whether I will adopt this approach. I think it is easier to write a method findRecent() which internally uses the find() method instead of writing a _findRecent() method as shown in the article.

By: Rafael Bandeira

Rafael Bandeira — Mon, 20 Oct 2008 19:39:30 +0000

@taylor: the snippet is very usefull but needs some fixes: first of all it will miss find('all') as there's no _findAll() method and second is that it's strtolower() on method's name takes a little bit of readability, don't you think?


$this->find('pricingreport'); 
// is a little bit worse than
$this->find('pricingReport');

$this->find('totalworkedtimereport');
// is much worse than 
$this->find('totalWorkedTimeReport');

ok it's about taste, but the find('all') is much more than an issue:


class AppModel extends Model {
	public function __construct($id = false, $table = null, $ds = null) {
		foreach(get_class_methods($this) as $method) {
			if (strpos($method, '_find') !== false) {
				$method = Inflector::variable(str_replace('_find', '', $method));
				$finders[$method] = true;
			}
		}
		$this->_findMethods = $finders + array('all' => true);
		parent::__construct($id, $table, $ds);
	}
}

@cakebaker: so far, have you started using it? I'm using it a lot, actually I only use it, all reports, views, tables and lists are generated this way... how about you?