Evolutions: Single semicolon—even in a comment—is treated as statement terminator

Double semicolon escapes are necessary in things like function bodies, but they are also needed in comments, which I believe is unintuitive. For example, if my evolution script were the following, I'd have a syntax error when running it:

CREATE TABLE foo(
  -- This is a test table; this line is erroneously treated as a syntax error because of the semicolon.
  id serial
);

The error that you get when running this is:

Database 'default' is in an inconsistent state!

We got the following error: ERROR: syntax error at end of input Position: 42 [ERROR:0, SQLSTATE:42601], while trying to run this SQL script:

1    # --- Rev:1,Ups - 15b2c43
2
3    CREATE TABLE foo(
4    -- This is a test table; this line is erroneously treated as a syntax error because of the semicolon.
5    id serial
6    );

Only by escaping the semicolon in the comment with a double semicolon (;;) does the script work. This can cause a lot of confusion—It took me an hour to find the cause in an 800-line evolution script—enough that it could be considered a bug.

Play Version (2.5.x / etc)

Play Version 2.5.3

API (Scala / Java / Neither / Both)

Scala

Operating System (Ubuntu 15.10 / MacOS 10.10 / Windows 10)

macOS Sierra (10.12.1)

JDK (Oracle 1.8.0_72, OpenJDK 1.8.x, Azul Zing)

java version "1.8.0_60"
Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)

Reproduce the issue with the shown evolution script, then trace the Play 2.5.3 evolution statement splitting around the comment containing a semicolon. Done means semicolons inside SQL comments no longer terminate the statement, with a regression test covering the example.