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

Jose da Silva's Blog: Revisiting PHP 5.3 __invoke magic method

Arnold Daniels' Blog: An alternative way of EAV modeling

Zend Developer Zone: PHP and your domain model with Doctrine ORM

Christopher Jones' Blog: Installing Oracle XE on Ubuntu with PHP

PHPHacks.com: Creating charts with JGraph


Community Events





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


release laravel opinion interview community series podcast introduction example security list framework tool voicesoftheelephpant library version conference language composer symfony

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