Comments on: How Do You Edit a dump/exp/script File?

By: Log Buffer #109: A Carnival of the Vanities for DBAs

Log Buffer #109: A Carnival of the Vanities for DBAs — Fri, 08 Aug 2008 17:23:00 +0000

[…] Rusty Razor Blade’s Jon Haddad has a quick tip on executing MySQL queries within Vim. Along the same lines, Pythian’s Keith Murphy and his readers offer different ways to edit a dump/exp/script file. […]

By: LenZ

LenZ — Thu, 07 Aug 2008 10:14:24 +0000

The MySQL distribution actually ships with a small commandline tool that does exactly that - take a look at the “replace” command. I blogged about it some time ago:

http://www.lenzg.org/archives/149-A-hidden-gem-in-the-MySQL-distribution-replace.html

So in your case, you could do the following:

$ replace “INSERT” “INSERT REPLACE” — file.sql

By: Sheeri Cabral

Sheeri Cabral — Wed, 06 Aug 2008 11:52:50 +0000

Gregory — check your mysqldump options, you can stop mysqldump from throwing in “use databasename”.

By: Sheeri Cabral

Sheeri Cabral — Wed, 06 Aug 2008 11:52:15 +0000

The great thing about sed being a stream editor is that you can pipe the output of mysqldump directly into sed and then save the file….

so instead of

mysqldump > file.sql
you can do
mysqldump | sed ’s/^INSERT/REPLACE/’ > file.sql

(^ represents the beginning of the line, and I didn’t put the global switch “g”. Without “g” it will only replace the first instance per line, which is fine in this particular example…and yeah, people should definitely read the sed manual!)

By: Gregory Haase

Gregory Haase — Tue, 05 Aug 2008 19:18:51 +0000

In general, you have to be careful opening dumpfiles in editors of any kind. You can easily run into issues where special characters or binary data gets mangled. Strictly speaking, these are NOT ASCII text files.

For most cases, there are command line switches to mysqldump (e.g. –replace) that can be used to get the data in the format you want.

Another trick is to make two passes at mysqldump - the first one grabbing structure only (–no-data –routines –events), and the second one with –no-create-info. You can safely edit the first file even if you have blobs in your data model.

But the problem I run into most often is that the dump file contains “USE DATABASENAME” at the head, and if you don’t remove it, you could end up accidentally restoring your database to an old copy.

By: Giuseppe Maxia

Giuseppe Maxia — Tue, 05 Aug 2008 19:16:36 +0000

Hi Keith!
sed?
what about Perl?

http://datacharmer.blogspot.com/2008/08/editing-dump-file-from-airport.html

Cheers

Giuseppe