Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Just curious... are you using the 2009 O'Reilly book "Learning PHP, MySQL, &amp; JavaScript"? That's what I was using, and its directions were absolutely useless and wrong. I haven't bothered checking the errata, because there are so many issues with it that I can't imagine how it passed a simple proofread, and trial and error is usually a better guide for learning things like this.</p> <p>As a newbie, I just figured out this exact same problem after hours of frustration, basically trying to recover from various ways that an easyPHP update to 12.0 broke my development server.</p> <p>I'm sure you figured this out by now, but for the sake of giving a useful explanation to other users who share this problem/read the same error-ridden book, here's what worked for me, a Windows user:</p> <ol> <li>Open the <strong>shell</strong> command line, NOT the MySQL command line.</li> <li>Inside double quotes, list the full path name (from the name of the drive to the .exe). Because it's in quotes, spaces (such as in Program files (x86) are fine).</li> <li>After closing the quote, -u <em>username</em> -p <em>password database</em> > <em>destination.sql</em></li> <li>This will export the dump into the directory of the user that logged onto the command line. For me, the sql file was up in C:\Users\Me</li> <li>In the shell command line again, change mysqldump to the mysql in the directory that you'll be using. For me, I also modified the pathname of the exe to the updated folder (from "EasyPHP-5.3.9 etc." to "EasyPHP-12.0 etc")</li> <li>Put a -D in front of the database name</li> <li>Flip the direction of the arrow.</li> </ol> <p>Dump command:<br /><br /> "C:\Program Files (x86)\EasyPHP-5.3.9\mysql\bin\mysqldump.exe" -u root -p database > database_dump.sql</p> <p>Restore command:<br /><br /> "C:\Program Files (x86)\EasyPHP-12.0\mysql\bin\mysql.exe" -u root -p -D database &lt; database_dump.sql</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload