thanks for answering, and of course each ORM has it's good parts. For sure specific data logic has to be developed directly using ORM, and I never said we have to ban ORM specific dev nor that DbFinder has to implement nested set or geocode behavior. I just find it's a pity it is no more maintained. In some cases such as newsletter, application preferences, template switcher, even a simple blog, logic is very simple and it should be possible to have it ORM agnostic. It's all about avoiding code replication when it is possible, and DbFinder has been developed for that.
I really think a first class framework as symfony has to furnish such a thing, that's all. -- You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en.
