On Wed, 21 Apr 2010, Parijat Kalia wrote: > The one sucky part about symfony for me is how to handle database changes. I > mean, if I need to go about changing db fields, then must i loose all my > existing data? > > I am sure there is a very easy way around this, coz if there is a long way > around it, then that would be crazy as db changes happen all the time.
Migrations are your friend. (If you're still using Propel, then this might be incentive to switch to Doctrine :-) http://www.doctrine-project.org/documentation/cookbook/1_0/en/symfony-and-doctrine-migrations This questions comes up on the list every month or two... -- -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
