On development machine I have initial fixtures and really don't care about anything, just using rebuild-all when needed and data-dump to keep changes. When it's time to deploy to production or staging server, I am preparing migrations, initially it's easy, later you just have to add "up" and "down" instruction according to changes happen in models since last deployment. This might be a problem for large systems only with some really major changes...
As for me, the migrations doing it's job pretty nice. So, I am using it and hoping to see plugins(RoR like) based migration in the near future :) Also going to give a try to sfPropelSqlDiffPlugin, looks promising. http://www.symfony-project.org/plugins/sfPropelSqlDiffPlugin Would be great to have something similar for migrations, i.e. to diff migrations with current schema. Thanks. Daniel wrote: > Went trough > http://groups.google.com/group/symfony-users/browse_thread/thread/1c2c4fa066c59171?hl=en > discussing best way to get data from database into YAML. > > A follow up question popped up regarding the best way to do changes to > a db model. > > I usually do the changes in my schema file. Afterwards i run > propel:make-model. But after that I usually don't want to run build- > sql and insert-sql as the latter drops my tables. Instead I manually > do the changes to the tables (via manually ALTERing the tables). > > As Symfony have surprised me and my team before I guess this problem > is solved already. > > > > Is there any easier, more automatic way to update a data model which > already contains data? > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
