"Best Practices" for handling changes to database schema?

• Previous message: Gili: "Re: CASCADE support?"
• In reply to: Gili: "CASCADE support?"
• Next in thread: Gentry, Michael \(Contractor\): "RE: "Best Practices" for handling changes to database schema?"
• Reply: Gentry, Michael \(Contractor\): "RE: "Best Practices" for handling changes to database schema?"
• Reply: Gentry, Michael \(Contractor\): "RE: "Best Practices" for handling changes to database schema?"
• Reply: Neil Pierson: "Re: "Best Practices" for handling changes to database schema?"
• Reply: Jeff de Vries: "Trying to set qualifier on a saved query?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I used Modeler to reverse engineer an existing database. I make several
changes (flattening relationships, changing some names, etc), and saved
out my cayenne.xml file. I now need to add another column to one table
back on the database. Do I need to re-reverse engineer the whole
database and make all my changes all over again, or is there a "better way"?

Thanks,
Jeff de Vries

• Next message: Gentry, Michael \(Contractor\): "RE: "Best Practices" for handling changes to database schema?"
• Previous message: Gili: "Re: CASCADE support?"
• In reply to: Gili: "CASCADE support?"
• Next in thread: Gentry, Michael \(Contractor\): "RE: "Best Practices" for handling changes to database schema?"
• Reply: Gentry, Michael \(Contractor\): "RE: "Best Practices" for handling changes to database schema?"
• Reply: Gentry, Michael \(Contractor\): "RE: "Best Practices" for handling changes to database schema?"
• Reply: Neil Pierson: "Re: "Best Practices" for handling changes to database schema?"
• Reply: Jeff de Vries: "Trying to set qualifier on a saved query?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2.0.0 : Wed Aug 31 2005 - 14:01:17 EDT