Could --dry-run do deeper validation?

[pfnsec]

Is your feature request related to a problem? Please describe.
We are running schemachange in CI. Before a merge, we run it with --dry-run, but by design, it doesn't catch basic SQL syntax errors. We'd like to have a CI step that gives us a stronger guarantee of fitness for the migrations staged in a PR.

Describe the solution you'd like
Perhaps a more exhaustive test run of the syntax could be implemented? It could be an intermediate step like schemachange --plan. This would enhance schemachange's utility to us as part of our CI flow.