GNIP 19 GeoNode Migrations

GNIP 19 - GeoNode Migrations

Overview

It is proposed to add django-south http://south.aeracode.org/ as a hard dependency in GeoNode to assist with database schema migrations.

Some initial work has been done by Eldarion on adding south and adding migrations for apps they are developing.

https://github.com/eldarion/geonode/commit/6cb07de4ecbad7be3ae4fefbbfdafb1e3ef1ec5d https://github.com/eldarion/geonode/commit/4f571c77b40751253344df3f24eec7d6467abd1f https://github.com/eldarion/geonode/commit/42d23cf3474ea54a26e63c6e08116f5030e0827f

Proposed By

Jeffrey Johnson

Assigned to Release

1.2

State

Implemented

Motivation

Currently the GeoNode development team makes every effort to NOT make changes to the database schema unless they are absolutely necessary in order to avoid problems with Database Schema migration. There are several new pieces of functionality that are being developed which will require that we make database changes in order for them to work properly. It makes sense to address the issue of migrations now rather than continue trying to avoid it.

Proposal

It is proposed to add django-south as a hard dependency and document its use going forward.

Issues

TODO:

Testing

TODO:

Alternatives

Do nothing. Continue avoiding database changes.

Feedback

Voting