- Squitch - ?
- DBIx::Class::Migration - verbose but powerful. Use dbic-migration alongside dbicdump
- DBIx::Migration - not the same as, or as good as DBIx::Class::Migration
- DBIx::Migration::Directories
- DBIx::Patcher (used at NAP)
- perl-Monorail - ?
- App::JESP - ?
- Migraine
- Mojolicious::Command::migration - thin wrapper for dbic-migration
- Database::Migrator
- SQL::Schema::Versioned
- mimi
- gh-ost - massive overkill for small apps
A piggy bank of commands, fixes, succinct reviews, some mini articles and technical opinions from a (mostly) Perl developer.
Jump to
Showing posts with label change control. Show all posts
Showing posts with label change control. Show all posts
Database schema management systems
A list:
System maintenance
There is a reason we have a process of change control. It has become a dirty word in some departments, but the bare minimum is:
- making a change in the development environment
- testing it, preferably by more than one person/team
- packaging up the release and labeling it properly
- making a formal request to deploy it, including roll-back instructions
In addition, a precedent should never be set to fix something that another department has broken!
Labels:
article,
change control,
companies,
productivity,
release cycle,
system
Subscribe to:
Posts (Atom)