Wednesday 15 September 2010 11:15:34 am

So simple. It can easily understandable even for a newbie.

I appreciate your time and work for this great article.

I have a suggestion ,it would have been a better idea if you could include some cutom fetch example that make some sense

in the php method ,

<span>public</span> <a href="http://www.php.net/static" mce_href="http://www.php.net/static" target="ez_no_documentation"><span>static</span></a> <span>function</span> getMyFetchFunctionResult<span></span>

Romeo Antony

Oman , GCC

Wednesday 15 September 2010 1:21:27 pm

Thank you for the followup Jerome.

In function , you did like this

$result = array(
'first_key' => 'foo',
'second_key' => 'bar'
)

I know ,It is for simplicity. instead of that, if you show some meaningful custom fetch function operations with parameters could be really helpful .Since this article is fully focusing on extending custom fetch function .

Anyway I really enjoyed this article. This week beginning I have just started on try to develop simple extensions. This article is an additional help for my tries.

Monday 20 September 2010 3:49:45 am

Nice article, however I don't see the need to have an catch all try block on the "How it works" page. 1. No fetch functions use exceptions, they use null/false normally to indicate issues. 2. pokemon exceptions handling ( "Gotta Catch 'Em All" ) ? :)

As in: basically only use try block if the api your using uses exceptions, and then stricten the match for those exceptions instead of unintentionally catching exceptions your not supposed to handle(that might show up in the future, lets say for mvc exceptions for instance).

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Monday 04 October 2010 1:49:42 am

Hi Jérôme,

Clear and neat tutorial ... perfect work.

Joël