I am facing an issue with a MySql dump file (i.e mydump.mysql) generated by a Drupal export module. I am trying to import it on a local Drupal installation via Acquia Dev Desktop.

When browsing for my dump file, this application filters for .sql, .sql.gz and .mysql files. I thought it would load my .mysql easily, but I get an unsupported file type .mysql error.

Is there a way to convert my .mysql file into a .sql file, knowing that I don't have access to the original database used to generate my mydump.mysql? I would like to try to feed a .sql file to Acquia Dev Desktop instead.

P.S.: I am on Windows 7 if this is relevant. Thanks.

  • 1
    Can't you just change the extension via Windows Explorer or command line, or copy the file giving the new copy the .sql extension? This doesn't sound like a conversion to me, just a rename. – Aaron Bertrand Feb 14 '12 at 20:59
  • Please copy the first 10 lines of mydump.mysql and paste it in your question. – RolandoMySQLDBA Feb 14 '12 at 21:14
  • @Aaron I tried a simple rename, but I when I try to load the file, I get a 'The Pipe is being closed' error message after a couple of seconds. – Jérôme Verstrynge Feb 15 '12 at 8:10
  • @RolandoMySQLDBA I tried to open the file with Notepad++, but it seems like the content is binary. When I try to paste the 10 first lines here, SO only displays one unreadable character. – Jérôme Verstrynge Feb 15 '12 at 8:11
  • Have you tried renaming .mysql file to .sql file? – user6717 Feb 15 '12 at 10:51

For the records, I finally managed to load my dump into Acquia Dev Desktop after renaming the file to .sql and specifying/using exactly the same database name as the original database name.

I don't know what caused the original issue or what solved it, since I don't believe the database name should be an issue at all.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.