#change-management
RSS- 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: Back to the VCS
https://justatheory.com/2012/06/sqitch-vcs-again
- The Ever Evolving Sqitch Plan
https://justatheory.com/2012/05/evolving-sqitch-plan
- Sqitch Symbolism
https://justatheory.com/2012/09/sqitch-symbolism
- Some Thoughts on Database Change Management
https://justatheory.com/2009/04/database-change-management
Database migration frameworks and ad-hoc solutions leave things…wanting. Herein lie some preliminary thoughts on how to solve this problem.
- Sqitch: Depend On It!
https://justatheory.com/2012/08/sqitch-depend-on-it
- Sqitch Update
https://justatheory.com/2012/04/sqitch-update
A quick update on Sqitch. I started implementation about a couple of weeks ago. It’s coming a long a bit more slowly than I’d like, given that I need to give a presentation on it soon. But I did things a little differently than I usually do with project like this: I wrote documentation first. In addition to the basic docs I posted a couple weeks back, I’ve written a tutorial. I put quite a lot of time into it, studying the Git interface as I did so, to try to develop useful workflows. The nice thing about this it that it will not only serve as the foundation for my presentation (PHEW! Half the work done already!), but it also serves as a design specification.
- Sqitch v1.0.0
https://justatheory.com/2019/06/sqitch-v1.0.0
After seven years of development and production database deployments, I finally put in the effort to release v1.0.0.
- 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.
- Sqitch Update: Almost Usable
https://justatheory.com/2012/07/sqitch-almost-usable
- 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
- Sqitch v0.80: Now With More You
https://justatheory.com/2012/08/sqitch-more-you
- Sqitch: Rename Step Objects and the SQL Directory?
https://justatheory.com/2012/06/sqitch-steps-to-change
After all of the thinking and rethinking about how to manage a Sqitch plan, I am just about done with all the changes to make it all work. One of the changes I’ve made is that tags are no longer objects that stand on their own between change steps, but are simply names the refer to specific change steps. Not only is this much more like how a VCS thinks of tags (basically another name for a single commit), but it also greatly simplifies the code for iterating over a plan and updating metadata in the database.
- Notes on Upcoming Sqitch Improvements
https://justatheory.com/2013/07/upcoming-sqitch-improvements
- Sqitch: Trust, But Verify
https://justatheory.com/2013/01/sqitch-trust-but-verify
- Sqitch Homebrew Tap
https://justatheory.com/2013/02/sqitch-homebrew-tap
If Sqitch is to succeed, it needs to get into the hands of as many people as possible. That means making it easy to install for people who are not Perl hackers and don’t want to deal with CPAN. The Sqitch Homebrew Tap is my first public stab at that. It provides a series of “Formulas” for Homebrew users to easily download, build, and install Sqitch and all of its dependencies.