#change-management
- VCS-Enabled SQL Change Management
https://justatheory.com/2012/01/vcs-sql-change-management/
Some thoughts on how to use VCS history to determine what changes need to be deployed or reverted without relying on a configuration file.
- Sqitch Update: All Your Rebase Are...Never Mind
https://justatheory.com/2012/12/sqitch-rebase/
- SQL Change Management Sans Duplication
https://justatheory.com/2012/01/sql-change-management-sans-redundancy/
Here’s how I propose to eliminate the duplication of code between deploy and revert SQL change management scripts.
- Sqitch Update: Almost Usable
https://justatheory.com/2012/07/sqitch-almost-usable/
- Sqitch: Back to the VCS
https://justatheory.com/2012/06/sqitch-vcs-again/
- Sqitch: Depend On It!
https://justatheory.com/2012/08/sqitch-depend-on-it/
- Sqitch Symbolism
https://justatheory.com/2012/09/sqitch-symbolism/
- Simple SQL Change Management
https://justatheory.com/2012/01/simple-sql-change-management/
I’ve been thinking a lot about SQL change management. I think I may finally have cracked this thing wide open.
Follow #change-management
on RSS or use the
JSON API
curl -X GET \
-H "Content-type: application/json" \
-H "Accept: application/json" \
"https://octothorp.es/~/change-management"