Comments on: Database schema under version control https://shlomi-noach.github.io/blog/mysql/database-schema-under-version-control Blog by Shlomi Noach Sun, 23 Jan 2011 10:25:32 +0000 hourly 1 https://wordpress.org/?v=5.3.3 By: Christophe Fondacci https://shlomi-noach.github.io/blog/mysql/database-schema-under-version-control/comment-page-1#comment-28170 Sun, 23 Jan 2011 10:25:32 +0000 https://shlomi-noach.github.io/blog/?p=2215#comment-28170 For version control, you might be interested in taking a look at the neXtep designer project.

It is a database development environment where you develop on a version control repository. You work on the model, and the system handles all generation of the SQL delta scripts for you. You can synchronize your current developments at any time with a target database of your choice, where you can integrate changes from the database or push developments from the repository.

This is a free opensource GPL product whose aim is to solve many problems related to database version control and developments. We are trying to gather people around the project to get more feedbacks on it.
Tell me what you think.

Here is the link to the project website :
http://www.nextep-softwares.com
And another link of the product’s wiki containing more information on the concepts, tutorials, technical information :
http://www.nextep-softwares.com/wiki

Kind regards,
Christophe

]]> By: shlomi https://shlomi-noach.github.io/blog/mysql/database-schema-under-version-control/comment-page-1#comment-12614 Sat, 24 Apr 2010 04:00:56 +0000 https://shlomi-noach.github.io/blog/?p=2215#comment-12614 @Peter,

If my memory serves me right, one reason for this was to be certain that auto_increment values would be consistent in a replication setup from the dump (when latest innodb rows are removed, auto_increment remains highest removed row, but that would not reflect in a server built from the dump)

]]> By: Peter Laursen https://shlomi-noach.github.io/blog/mysql/database-schema-under-version-control/comment-page-1#comment-12479 Thu, 22 Apr 2010 09:43:36 +0000 https://shlomi-noach.github.io/blog/?p=2215#comment-12479 This post reminds me that I have always been (almost) angry about that AUTO_INCREMENT = XXXX information was added to SHOW CREATE TABLE. This makes it harder to get importable structural-only information from a table. It has broken many tools making use of SHOW CREATE. Integration with version control as described here is another example. Any idea why they did this? Some ugly workaround for a InnoDB slowness issue maybe?

]]>