On Sun, Nov 23, 2008 at 6:10 PM, thebigdog <[EMAIL PROTECTED]> wrote:
> > I do believe this is more under Database versions, and migrating changes > > from a Developers Database Sandbox to the Staging and then Production > > Databases. When it comes to a large development team, sometime's it's > best > > to version both the Code and Database, per Developer. > > I am wondering why you would need a tool for this. I have worked with > numerous > developers and just used update scripts. Is there really a requirement for > a > tool to handle the update scripts for a database? > > > -- > thebigdog > Yes.. This comes into play in a few areas: 1. Automated Testing 2. Large (20+) development teams 3. Multiple projects happening at the same time Let's key off of a those. 1) Automated Testing-- Automated Testing can use a Code Revision, and Database Revision to determine when a bug is introduced, and why, then, automatically scale back to the working copy, alerting the developer in charge of the code commit, who can then fix it, put it back up, and Automated Testing can continue. 2) Large Development Teams-- When you have 20+ people working off of the same Development database, changes get lost and some people may over-write others database updates, or, cause an error and restore a table from a backup -- losing what other developers have done. It solves the need for communication between developers every time they need to do anything with the database, and saves a lot of time in troubleshooting and correcting errors. 3) Multiple Projects-- When you have, 3, 5, 10, or more projects going on simultaneously, someone may make changes to a database (drop this column, add this replacement column) on a Project A slated for 2 weeks out, and another developer may have Project B going for 1 week out, and wants to push out the same table, without worry of dropping a column for a project that won't be ready for a week longer than the current deadline of Project A... This causes huge concerns, such as multiple developers using the same sandbox, modifying code for 2 different projects,and pushing out errors.. There are more, more in-depth reasons, but these stand out the most. You don't trust the Developer to remember every line of code they modified after 3 months on a project, why would you expect them to remember every Database change? -Will _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
