Support for multiple statements when using external SQL file

I’ve setup my database.json — which is definitely being used — to specify multipleStatements: true:

{
    "mysql": {
        "ENV": "DB_CREDENTIALS",
        "multipleStatements": true,
        "native": true
    }
}

However, when I try to migrate the following SQL migration — which was created by using db-migrate create add-quotes --sql-file -e mysql — I get an error that suggests multiple statements aren’t supported when using --sql-file:

CREATE TABLE `cocktails` (
  `id` int(11) unsigned NOT NULL AUTO_INCREMENT,
  `name` varchar(64) COLLATE utf8_unicode_ci DEFAULT NULL,
  `slug` varchar(64) COLLATE utf8_unicode_ci DEFAULT NULL,
  `description` mediumtext COLLATE utf8_unicode_ci,
  `date_added` date DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

CREATE TABLE `quotes` (
  `id` int(11) unsigned NOT NULL AUTO_INCREMENT,
  `quote` varchar(255) COLLATE utf8_unicode_ci NOT NULL,
  `name` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL,
  `date` date NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

Which produces the following error:

Error: ER_PARSE_ERROR: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘CREATE TABLE quotes ( id int(11) unsigned NOT NULL AUTO_INCREMENT, `quot’ at line 10

<bountysource-plugin>

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>

[bhubr]

Just throwing my two cents in. db-migrate is really great, but apart from deciding if multipleStatements should be made a default, there is definitely, IMHO, a documentation issue.

The usage page mentions the --sql-file, and states that “the sql files will have the following content:”

/* Replace with your SQL commands */

Now, correct me if I’m wrong, but SQL commands seems to imply that you may put several of them, which I incorrectly assumed. So I lost a fair amount of time trying to fix an SQL schema that wasn’t broken, just because I got the exact same error as the OP when trying to import a schema.

It might be worth mentioning, in the auto-generated SQL files, that issuing multiple statements without specifying multipleStatements will result in errors!

[captainamerican]

If you’re using the DATABASE_URL environmental variable, you can bypass this bug in the following manner:

mysql://user:pass@host/database?multipleStatements=true

I’m don’t why this works. It was a last ditch effort before I got rid of db-migrate.