The SchemaBootstrap class executes statements using the ";" (semicolon) character exclusively as a separator to determine when a statement is "complete" and then execute the statement buffer.
This can be problematic when adding triggers, functions, stored procedures, etc., for applications with special needs, since the semicolon is usually an intrinsic part of the syntax that cannot be removed (in the manner that the SchemaBootstrap class removes it) without breaking the syntax.
I would recommend the addition of two "controller" statements (like --INCLUDE or --ASSIGN) to allow the temporary (per-statement) definition of a separator, i.e. such as:
This would be equivalent to the "delimiter X" statement some SQL languages support, and would avoid having to employ a more complex SQL parser in order to support the execution of these complex statements.