Yes, I did some checking on the latest version, and it appears that it adds that line in the background. The only solution I saw was a hack of the code, which of course is not an option if you're using it from a shared hosting control panel.Susan, I had a lengthy session yesterday with one of the hosting company's technicians. He seems open to making this problem go away. Can you elaborate upon or provide a link to the hack you referred to above?
This behavior did not happen by default in version 3. A quick fix, actually a hack and thus not the desirable solution, is to edit the export class file located in libraries/plugins/export/ExportSql.class.php and force the CREATE and USE statements to be commented out by adding "-- " before them, as such: Line 709
$create_query = '-- CREATE DATABASE IF NOT EXISTS '
Line 734
'-- USE ' . PMA_Util::backquoteCompat($db, $compat)
From a stackoverflow response I found via Google - http://stackoverflow.com/questions/16892806/how-to-remove-create-database-if-not-exists-statement-from-export-in-phpmyadmiThanks Susan. That item is spot on. I thought that post was written by me. Anyway, just sent it over to our hosting company to see if they're up to installing a hack.
This behavior did not happen by default in version 3. A quick fix, actually a hack and thus not the desirable solution, is to edit the export class file located in libraries/plugins/export/ExportSql.class.php and force the CREATE and USE statements to be commented out by adding "-- " before them, as such: Line 709
$create_query = '-- CREATE DATABASE IF NOT EXISTS '
Line 734
'-- USE ' . PMA_Util::backquoteCompat($db, $compat)
Google is your friendSusan, I can't tell you how many times Google saved my bacon. If they began assessing me $5 a month for their service I'd likely pay it (albeit begrudgingly). Hope they're not reading this.