Changes between Version 17 and Version 18 of BluePrintDatabaseMigration
- Timestamp:
- 04/07/11 18:09:40 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrintDatabaseMigration
v17 v18 6 6 This project involves raw database operations on live user data, where the results must be carefully validated to avoid unrecoverable data loss. It will require knowledge of SQL and database administration, code generation or an equivalent means of specifying the process of converting a database, providing a UI when human assistance is needed to specify the conversion. It will also involve a knowledge of Web2py and DAL. 7 7 8 == = Motivation ===8 == Motivation == 9 9 10 10 Far too often, people make changes to the database schema or to the data with which the database is initially populated. This causes pain and suffering for anyone with a live Eden instance who needs to upgrade their Eden software. … … 58 58 59 59 60 ==== Fran's comments ==== 61 {{{ 60 === Fran's comments === 62 61 I don't understand where the proposed UI fits. 63 62 … … 77 76 78 77 A later enhancement would eb to warp this all up into a web-baed interface for handling updates - maybe GSoC 2012... 79 }}} 80 === Existing Tools === 78 79 80 == Existing Tools == 81 81 We use dbstruct to handle some types of migration: 82 82 * MySQL: http://eden.sahanafoundation.org/browser/static/scripts/tools/dbstruct_mysql.py … … 99 99 be no constraint issues when it's loaded. 100 100 101 == = Some suggested subsets for GSoC ===101 == Some suggested subsets for GSoC == 102 102 103 103 This seems to fall naturally into three pieces:
