> > Allowing any developer access to modify the database without express > permission or doing an impact analysis is asking for trouble. > > Great point.
> > In reading about CodeIgniter's database migration tool - it allows the > developer > to do the following (granted i only reviewed a small portion and have not > used > the tool so this might not be everything): > > '* Each individual in a team is supposedly working on their own > installation of > your system. > * Whenever a team member makes a change to their database schema, he > extracts > that change into a class called a "migration". > * When he is done working, he can move those "changes" to any other > environment > (the "live" environment, for example) and "install" each migration' > - CodeIgnitor > > One thing that is unsettling to me is the fact that any developer can make > changes and add that to the code base. Here in lies the issue - (IMHO) not > every > developer should be making the changes to the database that could be added > to a > production db. I don't want jr developers making changes to my db. I > think > your statements are true that there needs to be tons of communication and i > think there needs to be something to prohibit developers from making > changes > without some method to manage those changes. For this reason I am a big > fan of > code and database reviews and analysis before that code is introduced into > a > production baseline. > > > -- > thebigdog > thebigdog, yes, I was referring to "migrating" changes from a development database to production. As in keeping track of additions and changes to the database during development of a project. The reason I was interested in such a system comes from a project I was involved with part-time this last summer. There were 4 full time developers working on this project, and I only worked on it 2 or 3 days of the week. I only had access to my local copy of the code and database. I found it very difficult to keep my database in sync with the main development database. The did keep a file with all the database scripts in it, but it was hard to know which ones I had already applied to my copy of the database and they didn't have any of the data that the application needed; such as menu items and other things. I think that for smaller groups a tool to help manage the database could be very helpful. I just haven't tried it yet, so I was wondering if anyone else had any experience with something similar. Thanks for sharing your experiences. I do think that having to request a change to the database would ameliorate a lot of the problems we ran into. Dave _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
