On Fri, May 28, 2004 at 03:05:53PM +0300, Victoria Reznichenko wrote: > Josef Karthauser <[EMAIL PROTECTED]> wrote: > > In the old days of mysql (version 3.x) the mysqldump command would > > produce one text line per database row, but since then it appears to > > have been replaced with an "extended insert" format which is more > > efficient for getting data back into the database. > > > > The old format was good however for running "diff" on so that it was > > easy to just dump the database and then compare it to a previous dump > > using "diff -u". Only the rows that had changed would show up. With > > the new format that doesn't work because many rows are now on the same > > textual line. > > > > Is there any way to pursuade the mysqldump from 4.1.x to use a single > > line per row insert format? I've not seen anything in the manual page, > > and I find it a loss of functionality. > > Use --skip-extended-insert or --skip-opt options of mysqldump. >
Yes, that's the ticket. Shouldn't this be documented in the manual page for mysqldump? (And in the dig mysql manual documentation?) Joe -- Josef Karthauser ([EMAIL PROTECTED]) http://www.josef-k.net/ FreeBSD (cvs meister, admin and hacker) http://www.uk.FreeBSD.org/ Physics Particle Theory (student) http://www.pact.cpes.sussex.ac.uk/ ================ An eclectic mix of fact and theory. =================
pgpa1KS7dnYG5.pgp
Description: PGP signature
