Question

I’ve got a site that requires manual creation of the database tables on install. At the moment they are saved (along with any initial data) in a collection of .sql files.

I’ve tried to auto-create using exec() with CLI MySQL and while it works on a few platforms it’s fairly flakey and I don’t really like doing it this way, plus it is hard to debug errors and is far from bulletproof (especially if the MySQL executable isn’t in the system path).

Is there a better way of doing this? The MySQL query() command only allows one sql statement per query (which is the sticking point).

MySQLi I’ve heard may solve some of these issues but I am fairly invested in the original MySQL library but would be willing to switch provided it’s stable, compatible and is commonly supported on a standard server build and is an improvement in general.

Failing this I’d probably be willing to do some sort of creation from a PHP array/data structure – which is arguably cleaner as it would be able to update tables to match the schema in situ. I am assuming this may be a problem that has already been solved, so any links to any example implementation with pro’s/con’s would be useful!

Thanks in advance for any insight.

Answer 1

Apparently you can pass 65536 as client flag when connecting to the datebase to allow multi queries, e.g. making use of ; in one SQL string.

You could also just read in the contents of the SQL files, explode by ; if necessary and run the queries inside a transaction to make sure all queries execute properly.

Another option would be to have a look at Phing and dbdeploy to manage databases.