Issue copied from google code.
What steps will reproduce the problem?
- Set up a migration that contains a line comment that includes a semicolon
- Execute the migration
What is the expected output? What do you see instead?
Expected: the line comment is executed.
Actual: bering attempts to execute just the comment. With some databases, this provokes a JDBC error. (Seen on Oracle, but may apply to others.)
Issue copied from google code.
What steps will reproduce the problem?
What is the expected output? What do you see instead?
Expected: the line comment is executed.
Actual: bering attempts to execute just the comment. With some databases, this provokes a JDBC error. (Seen on Oracle, but may apply to others.)