With liquibase 1.9.5, I could use the element and include a file that might include the following SQL:
Host char(60) COLLATE utf8_bin NOT NULL DEFAULT ‘’,
PRIMARY KEY (
) ENGINE=MyISAM COMMENT=‘Host privileges; Merged with database privileges’;
I find that in 2.0.0, even when a delimiter exists in quotes (as the comment in the SQL above contains), liquibase will still use that to demarcate a statement. When liquibase attempts to execute the above, it misses everything after “Host privileges”, which of course results in an error.
Is this an intended change in behavior?
Since our “baseline” schema for liquibase is generated from a MySQL dump, and that dump does indeed include semicolons, this change is decidedly incovenient. Is there a way I can escape the semicolon?