[Cosmo-dev] bug: 7127 move ContentItem.content and content* properties to table fields

[Brian Moseley]

On 10/19/06, Randy Letness <randy at osafoundation.org> wrote:

> Ideally we would have a Migration object for each release that does all
> this, and then a 0.5 Cosmo can be upgraded to 0.7 by executing the 0.6
> Migration and then the 0.7 Migration.

i'd prefer to be even more granular. as this particular change points
out, there will be multiple schema changes during development of a
particular version. i think the "cosmodb schema version" should be
decoupled from the release version.

an alternate way to handle this might be to provide external sql scripts that:

1) an admin can feed to his db server in an offline upgrade process
2) the server can use to upgrade in place

probably should be able to disable in place upgrades for admins who
prefer to do it manually.