Comments on: Ok, so Doctrine.. Part 2 http://www.symfonylab.com/ok-so-doctrine-part-2/ Everything you wanted to know about Symfony framework but did not know who to ask! Fri, 27 Apr 2012 14:49:28 -0700 http://wordpress.org/?v=2.9.2 hourly 1 By: daved http://www.symfonylab.com/ok-so-doctrine-part-2/comment-page-1/#comment-822 daved Sat, 26 Jun 2010 22:16:59 +0000 http://www.symfonylab.com/?p=223#comment-822 i think it's good because with only one ORM symf can focus on better. and I think Doctrine is very powerful (that's for it I left zend) but is miss an easy tool to generate plugins! I agree we lost a lot of times i think it’s good because with only one ORM symf can focus on better. and I think Doctrine is very powerful (that’s for it I left zend)
but is miss an easy tool to generate plugins! I agree we lost a lot of times

]]> By: admin http://www.symfonylab.com/ok-so-doctrine-part-2/comment-page-1/#comment-678 admin Sun, 11 Oct 2009 20:43:30 +0000 http://www.symfonylab.com/?p=223#comment-678 Absolutely agree. I had some thoughts today and came to conclusion that there is also tactical element in switching Symfony to Doctrine by default. So I guess it's because of Doctrine's lead developer is Jonathan Wage (http://twitter.com/jwage). He is great symfony contributor and person related with (read "loyal to") symfony project. So I guess at this point it's easier for SensioLabs to coordinate and affect Doctrine development which was not possible with Propel. The similar situation happened to Swift mailer project which is now managed by Fabien Potencier (http://twitter.com/fabpot). Main conclusion I made is - from now Doctrine will play much more important role and probably community by inertia will keep producing some Propel-oriented plugins but for long term - Propel will be moving away from Symfony scene. So that's what we should be ready for :-) Absolutely agree.
I had some thoughts today and came to conclusion that there is also tactical element in switching Symfony to Doctrine by default. So I guess it’s because of Doctrine’s lead developer is Jonathan Wage (http://twitter.com/jwage). He is great symfony contributor and person related with (read “loyal to”) symfony project. So I guess at this point it’s easier for SensioLabs to coordinate and affect Doctrine development which was not possible with Propel. The similar situation happened to Swift mailer project which is now managed by Fabien Potencier (http://twitter.com/fabpot).

Main conclusion I made is – from now Doctrine will play much more important role and probably community by inertia will keep producing some Propel-oriented plugins but for long term – Propel will be moving away from Symfony scene. So that’s what we should be ready for :-)

]]> By: DBA_Alex http://www.symfonylab.com/ok-so-doctrine-part-2/comment-page-1/#comment-677 DBA_Alex Sun, 11 Oct 2009 14:02:37 +0000 http://www.symfonylab.com/?p=223#comment-677 The other big issue with conversion of projects from Propel to Doctrine is the number of plugins that were built in Propel and therefore can't be used in the switch. It's going to be an interesting time being a symfony developer because either the plugins will need to be switched to using the dbFinderPlugin, which adds yet another layer to allow for conversion between Propel 1.2/1.3 and Doctrine, or it will need to be ported over and two different plugins be kept (here's looking at you sfGuardPlugin/sfDoctrineGuardPlugin). I imagine this is how the Doctrine users felt while all the plugins were being developed solely for Propel... The other big issue with conversion of projects from Propel to Doctrine is the number of plugins that were built in Propel and therefore can’t be used in the switch.

It’s going to be an interesting time being a symfony developer because either the plugins will need to be switched to using the dbFinderPlugin, which adds yet another layer to allow for conversion between Propel 1.2/1.3 and Doctrine, or it will need to be ported over and two different plugins be kept (here’s looking at you sfGuardPlugin/sfDoctrineGuardPlugin).

I imagine this is how the Doctrine users felt while all the plugins were being developed solely for Propel…

]]>