Here, Here. And the reason we normally want to go back in time, is when we are reintroducing a feature that we previously switched off.
Ie: Product Manager says, don't need xyz anymore, we remove the feature. Customer says, hey we were using that :) Regards Dale Fraser http://dale.fraser.id.au/blog -----Original Message----- From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Chris Velevitch Sent: Monday, 16 April 2007 5:42 PM To: cfaussie@googlegroups.com Subject: [cfaussie] Re: Version Controlling a Database In my view, rolling back database schema changes on a production database is a sure sign of something wrong with your development process that allows poorly thought out database changes that end up in production. This is because you need to consider the data that's been added, updated or deleted since the schema was updated. I agree on the value of using version control for the code changes the schema because it allows the capture of all changes made by multiple developers and to handle conflicts in concurrent changes. Chris -- Chris Velevitch Manager - Sydney Flash Platform Developers Group m: 0415 469 095 www.flashdev.org.au --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
