Changes between Initial Version and Version 1 of Event/2012/GSoC/DatabaseMigration


Ignore:
Timestamp:
06/08/12 05:04:39 (10 years ago)
Author:
anubhav
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Event/2012/GSoC/DatabaseMigration

    v1 v1  
     1== Database Migration : GSOC Project 2012 ==
     2
     3[http://eden.sahanafoundation.org/wiki/blueprint/dbmigration  BluePrint reference link]
     4
     5[https://github.com/anubhav929/Dbmigration-final- GitHub link]
     6
     7Weekly Meeting Schedule : Tuesday, 16:30 UTC
     8=== Personal Details ===
     9
     10==== Student ====
     11Name    : Anubhav Aggarwal\\
     12Country : India \\
     13Timezone: GMT + 5:30 \\
     14Email   : anubhav[at]gmail[dot]com \\
     15IRC Nick: anubhav \\
     16
     17==== Mentor ====
     18
     19Name : Pat Tressel\\
     20Email : ptressel[at]myuw[dot]net\\
     21IRC Nick : ptressel \\
     22
     23Name : Francis Boon\\
     24Email : francisboon[at]gmail[dot]com\\
     25IRC Nick : flavour \\
     26
     27=== Project Abstract ===
     28
     29The Database Migration project provides the developers with python scripts, to migrate or populate the database data between revisions .These scripts are provided according to the changes they have made in the database schema in comparison to the previous revision and also their intent behind there revision . This system also caters to the need of change in functionality of a field even if the database schema remains unchanged. 
     30\\
     31\\
     32
     33During this project, I will develop a detecting mechanism which determines the changes in the database schema with respect to the older revision using DAL. This detecting file can made to run after every commit.  Then ask the developer what his intent was behind those particular changes using the view and he would be required to match up the renamed tables and columns.If the changes that the developer requested were compatible then the developer will be given a python script that he can use in order to populate the database. However if the changes are not compatible like changing the type of an existing field in a table, we would have to ask him to write the mappings which will be used for populating the tuples. A python script will be generated according to the mapping he has provided.
     34\\
     35\\
     36
     37These script, which is generated and approved by the developer is stored in a folder for the use of System Admin , and will be run using "git hooks" attached with the "git pull" which will make the migration script present in the revision (provided by developer ) run
     38
     39
     40
     41=== Project Goals and Plans===
     42||= Tasks =||= Desciption =||
     43|| Create Tracking schema Changes Script || This Phase includes creating python script that can generate the schema changes between a serialized DAL instance and the current database . This would generate the result in the form of 2 dicts one contains appeared and the other contains disappeared . ||
     44|| Creating Actual Migration Scripts ||These scripts are made for these scenarios -  Renaming a field, Adding New field, Deleting a field, Changing Type of a field  ||
     45|| Building Tests and Adding Git hooks with the git pulls for the Sysadmin || These are used when a pull request is accepted by the Sysadmin thus the migration script is run and tested from the consent of the sysadmin who is presented with the changes and the script build from the recommendations of the developer ,if any problems occur or changes needs to be done sysadmin can change the script ||
     46|| Adding The GUI for the developers who make the changes in their own forks || This is view by which the developer can express express his intents ,and give his recommendations about the changes , these will be reviewed by the sysadmin when we accepts his pull requests ||
     47\\
     48\\
     49\\
     50
     51||= Due Date =||= goal =||= Status =||
     52||||'''Second trimester (2 June - 9 July)'''||||
     53|| 10June || Proper documentation of the Project goals, Deciding on the project workflow and start the coding for the Tracking Phase ||  In Progress ||
     54|| 15 June || Tracking Schema Changes In topo order completed ||     ||
     55|| 24 June || Creating Actual Migration Scripts  ||     ||
     56|| 8 July || Building Tests and Adding Git hooks with the git pulls for the Sysadmin  ||     ||
     57||||'''Third trimester (10 July - 13 August)'''||||
     58|| 25 July ||  Adding The GUI for the developers who make the changes in their own forks ||  ||   ||
     59|| 3 August || Testing ||  ||   ||
     60|| 13 August || Documentation Updates ||  ||   ||