#3892 (ok 4.0.0-rc4) SQL Export files are empty

[J.M. Rütter]

When exporting a database, the generated SQL file is empty. Only the phpMyAdmin comment headers and database collaction SET commands are written.

When exporting a database without writing a file, the following error is displayed:

No tables found in database.

Reproduced on demo.phpmyadmin.net running running Git revision RELEASE_4_0_0RC3-59-g658c79e from QA_4_0 branch.

[J.M. Rütter]

a564d981e9ef5022d69b2720d6a6126c73c74637 is the first bad commit
commit a564d981e9ef5022d69b2720d6a6126c73c74637
Author: Marc Delisle marc@infomarc.info
Date: Thu Apr 18 13:23:26 2013 -0400

Security: avoid $GLOBALS overwrite

:100644 100644 bbc682f2cd5d66c14cfa8701573a28d02129bd74 b7a8829d80cc1cf44c9ddec8c5537508d2c18a50 M export.php

[J.M. Rütter]

Pushed my fix to my fork:
https://github.com/mynetx/phpmyadmin/tree/MAINT_4_0_0

[Marc Delisle]

This problem is not when exporting a table, it's when exporting a database.

[J.M. Rütter]

• Description has changed:

Diff:

--- old
+++ new
@@ -1,6 +1,6 @@
-When exporting a table, the generated SQL file is empty. Only the phpMyAdmin comment headers and database collaction SET commands are written.
+When exporting a database, the generated SQL file is empty. Only the phpMyAdmin comment headers and database collaction SET commands are written.

-When exporting a table without writing a file, the following error is displayed:
+When exporting a database without writing a file, the following error is displayed:
 > No tables found in database.

 Reproduced on demo.phpmyadmin.net running running Git revision RELEASE_4_0_0RC3-59-g658c79e from QA_4_0 branch.