Hi Gert I will be using this approach soon, and hope to see it as a developer tool in symfony post 1.0, as the skeleton of the the tool is not Propel exclusive, so i think it should be a tool that is integrated into some kind of symfony 'deploy' and 'rollback' commands.
Thanks Joe On 14 Feb 2007, at 09:45, Gert Vrebos - Tactics bvba wrote: > Thanks Joe! > > I should have looked there of courseĀ > > Is this something to include in post-1.0 ? > > Gert. > > > > From: [email protected] [mailto:symfony- > [EMAIL PROTECTED] On Behalf Of Joe Simms > Sent: woensdag 14 februari 2007 10:30 > To: [email protected] > Subject: [symfony-devs] Re: Database upgrade/downgrade scripts > > > > Hi > > > > This has been published on the wiki > > > > http://www.symfony-project.com/trac/wiki/Migrations > > > > HTH > > > > Joe > > > > On 14 Feb 2007, at 08:58, Gert Vrebos - Tactics bvba wrote: > > > > > Hey, > > > > I was wondering if a database upgrade/downgrade system has been > considered yet. As I maintain several symfony projects at multiple > locations in multiple versions, I find it a hassle to make sure > database schemas are up to date. > > > > Currently I use the svn log of the data/*.sql files to do manual > upgrades, but a simple way (enforced or supported by symfony) to > create upgrade/downgrade scripts would make this process much > easier and far more reliable. > > > > I once found something similar in rails: > > http://media.rubyonrails.org/video/migrations.mov > > > > Have any steps been taken here, any ideas? > > > > Gert. > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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-devs?hl=en -~----------~----~----~----~------~----~------~--~---
