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 [email protected] 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 -~----------~----~----~----~------~----~------~--~---
