The differences between Propel and Doctrine are nontrivial. They have very different APIs.
The DbFinder plugin is meant to allow you to write ORM-portable code if your needs are simple: http://www.leftontheweb.com/message/DbFinderPlugin_The_ORM_isnt_important_anymore http://www.symfony-project.org/plugins/DbFinderPlugin However right now, according to the README, you can't use it with Symfony 1.2 and Doctrine (you can with Symfony 1.2 and Propel I gather), so its usefulness is rather limited at the moment. It does work with Doctrine in Symfony 1.1. I'm not sure what the 1.2 issue is, something about the admin generator theme not being bundled with Doctrine, I have no idea what that might have to do with DbFinder but I didn't write it, so that's not surprising. Of course using DbFinder imposes additional overhead on top of ORM overhead on top of PHP overhead on top of SQL server overhead on top of the file system. But that's life. (: My feeling is that you should make a choice and reap the full benefits of your ORM of choice. I strongly recommend Doctrine. A similar divide now exists where JavaScript frameworks are concerned. There I recommend jQuery. On Mon, Jan 19, 2009 at 3:00 PM, James <[email protected]> wrote: > > Is there no easy way to encapsulate both of them into the one plugin? > > > > -- Tom Boutell www.punkave.com www.boutell.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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-devs?hl=en -~----------~----~----~----~------~----~------~--~---
