(ok 2.11.4) space after COUNT breaks Export but not Query

This was discovered by a friend of mine in the lab who's new to SQL. He wrote "SELECT COUNT (*) FROM some_table ..." -- notice the space between COUNT and the parens. phpMyAdmin deals with this just fine, even though e.g. the command line MySQL interface complains. I suspect that the pretty-printer corrects this SQL before it's sent to the database. If, however, you try to export the results to a file, you get an error message -- apparently the original, un-sanitized SQL is sent directly to the database in this case.

This is a problem in general because it means that the in-browser results of a query may not match the results downloaded to a file. I believe that the same SQL should always be used for display results vs. export results. I don't care much whether this particular statement succeeds or fails, just that phpMyAdmin handles it consistently.

This bug has been verified with several recent (2.8.x, 2.10.x) versions, including the public demo server (2.11.0-dev, I believe). It occurs on the most recent versions of Safari and Firefox on OS X, and has been verified for both CSV and SQL export (presumably affects all types, however).