Database schema synchronization among developers

I am working on a project with several others. We all have local copies of the project, which is also constantly updated through svn repo.

Since we are at an early stage of development, we often change the layout of our database. This leads to a big problem when we synchronize our code, because we don’t have a great way to synchronize our database schemas.

What is an intuitive and easy way to synchronize a frequently changing database schema?

We work with CakePHP (not sure if this will help me find good solutions).

EDIT

Some tools for this type of work were found in CakePHP: http://book.cakephp.org/view/734/Schema-management-and-migrations

And here is an additional site: http://bakery.cakephp.org/articles/view/cake-db-migrations-v2-1

+5
source share
5 answers

Database migrations are an easy way to synchronize production databases. In essence, migration is a script that updates the database to the latest schema and populates new tables with the correct data, so they are stored in the correct state.

There are several functions provided by migrations:

  • Tools for automating the creation / updating of tables. Tools track the version of the schema and which scripts need to be run.
  • (#, ruby ​​ ..) sql. , , , , , .

, Ruby ( - Rails), # Java. , .

questions , , .

+2

CakePHP Database by Joel Moss .

github:

CakePHP 1.2 - script, CakePHP, , SQL. Migrations Ruby on Rails Pear MDB2, , .

Migrations . , Migrations . , , ​​ .

Migrations , . .

+1
+1

All Articles