Using a shared database for collaborative development

Question

Some of the people in my project seem to think that using a common development database with everyone who connects to it is the best thing. I think that this is not so, and each developer who has his own database (with periodic data updates) is the best. Am I right or wrong? Have you had any problems in any of these approaches?

Answer 1

Disk space and processor should be cheap enough so that each developer can run their own instance of the database , with automated assembly under version control. This is necessary so that developers can safely hack into the database in isolation from any other simultaneous hacking.

The caveat is that any changes they make to their private copy are useless to anyone else if they cannot be automatically applied during the build process. Thus, there must be a strong policy that the application code cannot depend on any state of the database, unless this state is represented by versioned versions in the DDL .

. : Evolutionary Database Design .

Answer 2

, , , .

, , .

, , , , , . .

Answer 3

(20 ), , .

, . , , (unit test, , , , ..).

, . , (, DB, , , ).

Answer 4

- , ?

Answer 5

, . .

, , . .

Answer 6

Hibernate , , ( "drop-drop" ). , . , .

, . . , , . , , , , .