Zendcasts Forum

hello ryan,

this is not really Zend_Form & doctrine related but I thought to mention it here...

I also started looking into Zend Framework & doctrine lately. Not doing very well btw...

I found this ressources pretty helpful:

This is the main article:

• http://ruben.savanne.be/articles/integr … d-doctrine

and this one refers to the previous article and offers a better implementation of the first part:

• http://www.danceric.net/2009/06/06/doct … framework/

Some other good resources are:

• http://weierophinney.net/matthew/archiv … ework.html

Best, Udo

I think that tying forms directly to entities is kind of a bad idea. Having something that rapidly generates your whole form for you is great if you just want to re-create the functionality of phpMyAdmin, however when you're writing web apps, you usually don't want to present the user with more than 10 form fields at a time to being with. Also, by binding them directly, you don't easily allow yourself the opportunity to intercept requests without using dependency injection, event listeners and decorators.

It's by no means a bad move to leverage these patterns, but I think a direct bind between Zend_Form and Doctrine can cause headaches down the line in terms of maintainability. Writing a Zend_Form and then setting up an array at the top with the necessary form fields that you want and their type etc... should be enough to automatically have Zend_Form loop through and create the new form elements.

Also, you can just set parameters in Doctrine using dynamic property assignment. e.g.

// checks for validation should be outside this
$entity = new MyEntity();

foreach($this->getParams as $p=>$v)
$entity->$p = $v;

$entity->save();