acquaman/acquaman — Issue #244: Non-trivial database upgrades
Author: dretrex
Created: 2012-03-01 03:19:02+00:00
State: open
Labels: Impact - High, Module - Data Management, Reason - Missing from API

With the framework (and the various apps) reaching a certain level of maturity, we are now coming into the realm where we are going to need to change existing databases in a non-trivial manner. The current database upgrade system has kept us going by being able to add columns to the existing tables, but if we want to proceed with even "minor" issues like #134 we are going to need to address this. We are definitely well beyond the point where we can just nuke a database and start over now. Mark, I don't remember where you outlined the types of upgrades that we need to consider but I do recall that there were four or five items. If you could link them or paste them in here that would be great.

We don't need to tackle them all in one go, but I feel we need to start thinking and planning on starting upgrading the database to be able to upgrade itself.