Migrations (cloned)

[mitsuhiko]

Cloned from #42:

---

Both the core and the plugins need some sort of migration framework. We should provide basic support for the core and the plugins for easier migrations. In general database layout changes should be reduced to a minimum but often you can't avoid that.

I would propose the following rules for database changes:

• once a plugin changed the database it will stay that way. no rollbacks on uninstallation
• plugins may never alter tables they have not created themselves!
• we add a migration_info table that contains the revision of the table and the table name for the update script.

Currently there is a way to register hand written update functions to the database layer and we will keep that but add a callable class that uses the proposed migration system from this ticket. We should then think about which databases we want to support and build functions that create alter statements for those databases.

[mitsuhiko]

grml

[mitsuhiko]

Milestone TextPress? 0.2 deleted