Hi Keith,
I agree that the data mapper is a good way to do Models etc but I
think the basic mapper shown in the quickstart does lead people into
trouble. If a newcomer follows the quickstart they soon find out that
modeling relations is very hard and they need an ORM...If we had
Doctrine 2 integration we can then show the data mapper pattern at its
best IMO.
I have had this concern with the quickstart for a while :)
You might be on a slippery slope here. I don't think Zend Framework
should dictate how people design their applications. Sure you can
encourage the use of good patterns, etc, but the choice is ultimately
the user's, and if the user is not capable of making those decisions
based on what they know, they might not be the right person for the
right job, to be frank...
I think one of ZF's unique selling points is that you can use a fraction
of the framework or stack all kinds of parts on each other, but (almost)
never being forced to use large code bases that you don't really need.
Good design doesn't dictate implementation, imo.
Also will we be deprecating Zend_Db as if we have tight Doctrine
integration is there any reason to keep Zend_Db?
Please keep Zend_Db! I've never used it, but making Zend Framework so
much dependent on another framework is never a good thing.
