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. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
