News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Jens Schauder's Blog:
One Database for Every Developer
August 24, 2010 @ 13:08:26

Jens Schauder has an interesting suggestion about the development environment for your projects - one database per developer.

How many databases run in your teams development environment? One for the complete team? I have seen many places like that, but please tell me: Why? You aren't working on a shared files system aren't you? How is a developer supposed to change the structure of that database without interrupting the work of the other developers? And just in case you haven't noticed: Pretty much every RDBMS vendor offers free versions of their database which can run on a developer machine.

He suggests that every developer needs their own isolated database instance where they can run rampant through the data and only cause any real issues (or correct major ones) without having to worry about the impact on others. Keeping them in sync is a whole different story, but can be helped with something like fixture data.

1 comment voice your opinion now!
database developer opinion isolation instance


blog comments powered by Disqus

Similar Posts

Zend Developer Zone: YAMMY!: DB to YAML conversion shell for CakePHP migrations

Job Posting: Dutch Open Projects BV Seeks PHP Developers (Leusden, The Netherlands)

IBM developerWorks: Five common PHP database problems

Ian Bicking's Blog: What PHP Deployment Gets Right

PHPClasses.org: Accelerate Web Pages Automatically using Google Mod_PageSpeed


Community Events





Don't see your event here?
Let us know!


package install podcast interview symfony api zendserver release series community update deployment language bugfix framework introduction tips library opinion laravel

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework