The default ORM will be doctrine, but propel will be supported, hopefully for a long time. I've used it in many projects, and I don't plan on switching - no reason to :) I started learning doctrine when propel seemed to be abandoned, so I can start new projects with it, but it got a new leader, and it's under development again. Unless you have a good reason to change, it's unneccesary - propel is alive, and it will do so for a while. If you followed the MVC separation, it will be a relatively easy task to switch - almost all the code you need to tamper with is in the model classes.
Gábor On Fri, Oct 2, 2009 at 09:15, Adrien Mogenet <adrien.moge...@gmail.com> wrote: > > Hi everyone, > > I developping a "simple" association manager, which can manage > members, fees, expenses, activities, accounts... > I'm using symfony 1.2 (trunk) and Propel 1.3 (trunk also). > > I know that symfony will evolve with Doctrine and not with Propel > anymore. > > So I'm wondering if it would be interesting to change my current ORM, > even if it's a small project. > Will it take a long time to perform this change ? > > Will it be interesting in the near future to change from Propel to > Doctrine ? > > > If you have any experience to share, feel free :-) > > -- > Adrien Mogenet > Looking for a 6 month internship, opensource/innovative projects > http://adrien.frenchcomp.net > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
