Rather than that, skip the create database statements [dev.mysql.com] in your original dump statement. Much easier.

That is a problem. I cannot re-generate the dump.

All I have is a dump file. Is it possible to skip the create database statement during import?

TIA

You could always use command line tools to find/replace the text in the dump file itself with your new database name.

Or you could import the file into your own development version/installation of MySQL and then dump it back out in the format you desire in order to move it on over and up to your new server.

Just some thoughts.

assuming a *nix command line you could do something like:
egrep -v '^CREATE DATABASE ¦^USE ' dump.sql ¦ mysql database_name

(replacing the broken pipe symbol with an actual pipe, of course)

WoW! That worked!

I'm confused though. What does egrep do? Replace the CREATE DATABASE with nothing? or does it comment out the line?

This is really great phranque.

Thanks!

egrep is a version of grep that lets you OR the regular expressions.
some versions of grep also work that way.
the regular expressions i used mean lines starting with "CREATE DATABASE " or "USE ".
-v is an option that inverts the match.
it therefore selects non-matching lines and passes them to grep's standard output which then gets piped into mysql's standard input.

So what your saying is egrep finds the pattern, skips that line and passes the rest to mysql's standard input, Correct?

TIA

yes, so keep in mind if the file is something like this it might not work correctly:

CREATE DATABASE /*!32312 IF NOT EXISTS*/
`database_name` /*!40100 DEFAULT CHARACTER SET latin1 */;

USE
`database_name`;

hmm.. I see the problem. I guess that would create an issue.

Thanks for that.