Weekly change scripts

Post #236,367 by Yendor 11/28/05 11:13:49 PM Reply	Weekly change scripts We have free reign to do as we please in the DV database. All database changes made during that week go into a numbered `mod_schema_##.sql` script. The client's DBAs then run this script (which we provide to them via email weekly) upon request. -YendorMike "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759 Historical Review of Pennsylvania
Post #236,482 by static 11/29/05 6:51:00 PM Reply	We do something like that. But on an even smaller scale. Given I am the DBA, and the developer for an internal app, most of the SQL changes I keep in version-specific files. The other 3 developers do changes in the local DB and then manually replicate them to production using MyAdmin (no, I don't like this, either). They are also conceptually resistant to version numbers in their product so I haven't even tried to get them to put SQL changes in versioned files... Wade. "Insert crowbar. Apply force."
Post #236,494 by drewk 11/29/05 10:19:26 PM Reply	Oh, that process will scale well :-/ === Purveyor of Doc Hope's [link\|http://DocHope.com\|fresh-baked dog biscuits and pet treats]. [link\|http://DocHope.com\|http://DocHope.com]
Post #236,686 by static 11/30/05 8:33:05 PM Reply	Tell me about it. If I lose development of my app, I will probably become the gatekeeper to the website releases. At which point, I will be insisting on version numbers and improving what currently passes for a release process. Taking their access away from the database will be harder... Wade. "Insert crowbar. Apply force."

Welcome to IWETHEY!