Backend

Solution for #34952-unsupport SQL error when importing sql from phpmyadmin on BAE

Bystab August 29, 2014

BAE provides developers with 1GB of free MySQL public database, which is enough for blogs and general CMS sites with bad database performance requirements, because it is free, there are some limitations on the use of SQL, and many of my friends who import databases into BAE's public MySQL database will get the error `#34952- unsupport SQL` error, this is because the imported sql has some BAE public database restricted characters.

The limitations of the BAE MySQL public database are as follows

The import of the database file is done asynchronously and needs to be committed before the actual import operation starts.

1. The maximum imported sql file cannot exceed 10G.
2. The following is prohibited in the imported sql file:
- astext*(
- envelope*(
- geometryn*(
- load_file*(
- grant*on*to

uuyi ：“*”means you can replace it with any character, BAE will filter the imported sql comprehensively, not only the sql statement can't contain the above statement, but also can't contain the above string in the numerical value, or else there will be a `#34952-unsupport SQL` leading to the sql The import fails.

In addition, the sql file is too large, will also lead to import failure, for larger sql file, it is recommended to use the “SQLDumpSplitter” tool to separate into small files, and then import.