Hi all, I am currently working on a Symfony application which is now in production. I still have to work on it so I have to set up some migrations but I must admit I'm completely lost here. I found a publication about setting up Doctrine Migrations (http://www.denderello.com/publications/guide-to-doctrine-migrations) but I have a few questions : - I don't know which case I'm in, should I use the "generate-migrations-db" or the "generate-migrations-model" task? What's the main difference?
- I suppose I have to run this task in my prod env., send it to my production server and then do the migration ? - As I already have saved datas, the procedure should be : mysqldump > somefile.sql symfony doctrine:drop-db symfony doctrine:build-db symfony doctrine:build --all-classes --and-migrate mysql < somefile.sql Am I right? What if my migration implies to drop an entire table? And finally, I heard about the "doctrine:generate-migrations-diff" task, this task will generate all the classes w/ the up/down methods? Thanks in advance for your answers, I'm kinda lost here oO Romain -- You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-us...@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.
