DbFinder is a bad choice for plugins that use the database in a nontrivial way. Yes, it unifies things at the simplest level (queries), but if you want to use the features that really distinguish one ORM from another (column aggregation inheritance, behaviors, migrations), you're out of luck. And it also adds overhead, slowing everything down.
Pick an ORM and help maintain plugins that use it. Say no to doing new projects with the other ORM. This has worked well for us - of course we support our earlier client sites built with Propel and Symfony 1.0 but new development is all Doctrine. On Dec 2, 7:40 am, MoUeTtE <[email protected]> wrote: > +1 > > I really do like symfony because I can develop plugins for everything > and easily re-use code in every applications that needs it. As I > remember, jobeet tutorial encourages you to do so, Pirum release let > me think that Sensio labs wants us to create our own repository too, > so everything encourages us to develop in plugin style. > > Thanks to that, applications upgrade can be done in 2 times: upgrade > all plugins, and then upgrade specific code for each application, so > the more you reuse your code, the less work you have to do for > upgrade, definitely that's great, I guess everybody will agree. > > In the meantime, ORM choice can depend on a lot of things: > - available ecosystem > - coding style experience > - behaviors > - client need > - already existing application... > > whatever it is, we usually have to use both ORMs (on different > projects of course), that's why I do not feel comfortable with > sticking to an ORM for plugin development. I even thought it was the > reason DbFinder was developed for, in order to have better > compatibility, better consistency and finally better ecosystem. > > Now, I just hope I will not have to redevelop and duplicate all my > work just to upgrade to the LTS version, because having production > projects using unmaintained libraries sucks. > > To go further, I'm wondering why this plugin isn't included with > default distribution in order to invite plugin developers to use it, > it would be so nice if sfGuard, media library, blog, forum, bugreport, > wiki or whatever application plugins were ORM agnostic. > > To conclude, that's definitely great to be able to choose your ORM, > and I'm aware that some functionalities could not be abstracted, but I > don't feel like it's an option anymore to have a maintained cross ORM > layer, mostly since Sensio has direct or indirect control over both > ORMs. > > Julien. -- 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.
