One more note for anyone else who runs into this problem: before running the source command, I dropped the database, recreated it, and then ran the mysqldump file into the empty database.
Matt > On 5/25/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > You can try doing the same steps, but break it down so that you do them one > > at a time. > > > > FIRST: open the MySQL CLI and attach to the server hosting the database you > > want to restore: > > > > (in a command shell) mysql -h [name or IP address of server] -u [your mysql > > account] -p > > > > Respond with your password when you are prompted. You should now be inside a > > MySQL client session. SECOND: make your destination database the active > > database for your session: > > > > USE [database name]; > > > > Third: process your MySQL dump file: > > > > source [fully-qualified path to dump file]; > > > > This is the slower, manual way of doing what your command line did all at > > once. One other idea, on Win32 machines there can be NO SPACE between the -p > > and the actual password (should you opt to put it in the command). You might > > try reformatting your command to remove that space. > > > > Shawn Green > > Database Administrator > > Unimin Corporation - Spruce Pine > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
