Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DO NOT MERGE. This PR is intended only for internal peer review prior to submitting the changes upstream, assuming we do eventually decide to do so.
A few things I don't like about the current implementation, but have yet to find a way to work around:
OutputInterface
instance in various areas. The core has its own output surrounding each migration that's difficult to reliably differentiate from dry run output. Because the core output would make copying and pasting the output of a dry run a lot more troublesome, the current approach simply changes the output verbosity level to squelch the core output.ReadOnlyProxyStatement
toOutputInterface
. The alternative is to duplicate the code to manipulate output verbosity levels inDryRunAdapter
, which would require overriding most if not all of the methods ofAdapterWrapper
to be able to call that code.ReadOnlyProxyConnection
toOutputInterface
. This is the best way I've found to make this interoperable with the rest of the core while still supporting the output of generated SQL statements.Refs cakephp#567