Good luck. ;-)

Re: “my code is written as a source for improvement and not to be considered as a quality standard” — yeah, that makes sense, and I took it as such. :-) Even so, all the ZF model code that I see tends to look like that; e.g., the Zend quick-start guide does mostly the same thing (models, mappers, etc).

Your (Michelangelo’s) article was of particular interest to me because it includes relationship data, and because you do such a good job of narrating your experience and showing the results (with full code download, no less). I thought it was a good example of what a real ZF codebase looks like when you begin to do non-trivial modelling. So, thanks for having written it in the first place. :-)

Today, Michelangelo van Dam posted this narrative relating his experience with Zend Framework models:…

I’d like the idea since I’ve heard so much about Doctrine with Zend Framework and I too would like to see it based on my example to have a good comparison and most importantly a good understanding on how it all relates to each other.

I’m looking forward to see some articles about this concept and I will in my turn investigate both tracks: Solar and ZF + Doctrine.

If you really want easy to create models, go with Doctrine. I’m building my base model classes by hand and not YAML because I want more control but the way Doctrine handles building the schema in the backend is great not only for development but testing as well.