msqldump and version control systems

Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

suityou01 replied

18 February 2010, 22:49
Originally posted by Sysman View Post

The aim:

During development I want to dump MySQL tables in a format suitable for input to a version control system (Thanks Nick).

Plain mysqldump outputs all the data on one line, and there will be changes to the table structure along the way as well, so I am thinking that what I want is:

a dump of the table structure

a dump of the data with one line per record

To be honest, before we even talk about version control, being able to do a diff at the (bash) command line would be rather useful.

I came across this blog entry, but it relates to MySQL 4.n and I'm now on 5.1.42.

I have a FreeBSD web server and OS X as a client (also with MySQL) to go at.

As a sanity check, am I going in the right direction here?

I have a bash script that extracts all the tables and tarballs them up. PM me I'll send it to you. Might be some stuff of use to pick the bones out of.
Leave a comment:
oversteer replied

18 February 2010, 12:22
You can dump table structure and table data to separate files (-d and -t). Might be worth dumping each table to separate files with -T. Don't forget stored procedures, triggers etc..
Leave a comment:
Sysman replied

18 February 2010, 12:18
Thanks ya'll.
Leave a comment:
NickFitz replied

17 February 2010, 18:04
--extended-insert=false will put each record into a separate INSERT.

EDIT: or wot chicane said
Leave a comment:
chicane replied

17 February 2010, 17:47
Not sure if I've got the wrong end of the stick here, but have you tried the...

Code:

--skip-extended-insert

...option to insert one row per line?

The table structure should sit on multiple lines by default - if not you might want to look at the format of carriage returns/line feeds within the dump file to see if they match the format used by your client.
Leave a comment:
Sysman started a topic msqldump and version control systems

17 February 2010, 17:32
msqldump and version control systems
The aim:

During development I want to dump MySQL tables in a format suitable for input to a version control system (Thanks Nick).

Plain mysqldump outputs all the data on one line, and there will be changes to the table structure along the way as well, so I am thinking that what I want is:

a dump of the table structure

a dump of the data with one line per record

To be honest, before we even talk about version control, being able to do a diff at the (bash) command line would be rather useful.

I came across this blog entry, but it relates to MySQL 4.n and I'm now on 5.1.42.

I have a FreeBSD web server and OS X as a client (also with MySQL) to go at.

As a sanity check, am I going in the right direction here?
Tags: None