A follow up to Thoughts on shared development databases. An overview of how personal databases work
Tag: databases
Thoughts on shared development databases
Trying a new format for sharing ideas, my thoughts, verbalized, enjoy. A fun little depiction:
Database “code” distinction
When considering how to improve dealing with changes to your database when releasing software, one simple distinction can help clear up a lot of confusion. There are two broad categories of things that change in a database. There are tables that contain data for your application. Unlike application code, these can’t be dropped and recreated each time you release. At…
What database schema comparisons can accomplish
When you wait until the last minute to deal with database changes, schema comparison is one of the tools necessary to reverse engineer what changed in your database. A schema comparison helps identify what changed about the structure of the database. For example, a table was added or a column was removed. Schema comparison doesn’t focus on what may or…
The consequences of waiting until the last minute to deal with the database
One common technique for managing database changes when releasing software is to establish a development database in addition to a production database. The development database is often a copy of production from some point in the past and serves as a point of experimentation for changes. Whether there’s one developer or many, this database becomes the record of truth for…