No. As you can see in the script, the semi-colon is the delimiter for the Insert statement. We still need it to be treated as such. The issue is that Liquibase is finding the semicolon inside the string to be inserted in a column. Unfortunately, the default endDelimiter is just a semicolon. I was able to get it to work by overriding the endDelimiter to ;$ for this changeset. That appears to make it look for a semicolon followed by an end of line character.