> > -----Original Message----- > From: Will Merrell [mailto:[EMAIL PROTECTED] > Sent: 20 February 2005 14:00 > To: Mysql Mailing list > Subject: How to Version Control a database > > > I have a project that involves several developers working on > their own machines. Each has a local copy of the database on > their own machine. Since we have some developers who develop > while not connected to the network, we cannot use a common database. > > How can I version control the database so that changes are > not lost or stepped on. Right now, we use mysqldump to dump > the database and version the dump file, but this still has > problems. Is there a better way? > > -- Will >
We treat the database as any other source code, i.e. we store three sql scripts in our repository and have a ant target that builds the database from these scripts. If anyone need to change the database layout, the default values or the test data then he or she just checkout the corresponding file and make the change. If it isn't stored in the repository, then it doesn't exist. /Thomas -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
