Quoting Jonathan Wilson <[EMAIL PROTECTED]>: > Matt, Ben: > > Thanks for the additional information - I'm looking forward to > setting up my separate development environment tonight. I appreciate > everyones comments and suggestions. > > BTW, I assume if you make schema changes to your development mysql > instance you manually implement(ALTER TABLE etc.) those changes in the > production database during the deploy process, yes? >
This is verging off topic and...I'm not entirely sure I understand your question, so I'll just tell you what I do and let you infer what you will :) This is kind of tailored toward mysql, but there are similar solutions for other db environments. Whenever I make a change to my dev DB, I make it using an SQL statement rather than through a "manager" application. (Or if I use a manager application, I make sure I use one that shows the SQL for the commands it is using) I set up a file with all of these SQL commands in it. In mysql, I can then do a "source filename" to get all of the changes applied to the database at once. Obviously I do it to the test db first, and then to the live site once we deploy. I could probably set up ant to run the sql "script" against the test/live dbs on deploy, but I don't do that right now. Matt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
