(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.) flyway migrate with some migrations that SELECT data.
What did you expect to see?
No output in the console
What did you see instead?
Tons of output. We upgraded from 5.1.4 Community to 5.2.4 Pro and now we see all this output. We'd rather not see it. Is there a way to suppress it?
The text was updated successfully, but these errors were encountered:
Ugh... the output from our tests is now massive and un-readable. I see you added a milestone for 6.0.0. A way to suppress this would be greatly appreciated. We'll see if we can get by until this without suppressing all the SELECT statements into temporary tables or variables.
In normal migrations I wouldn't expect many, or any SELECT statements, but I'm sure you can see how there are lots of them in our tests. Perhaps this is another aspect of #2256, to not show them by default.
@axelfontaine per the release notes, this was added in 5.0.0? Note that we upgraded from 5.1.4 Community to 5.2.4 Pro (on the trial), so we were already above 5.0.0. Is it one of the features that comes with Pro that doesn't come with Community? If so, is that documented anywhere?
The reason the docs are really sparse right is because it isn't doing very much. I however agree that it should definitely be possible to get the behavior of the Community Edition with the Pro Edition.
Currently considering the following: adding a results flag (default: true) for this. Setting it to falsewould then suppress the displaying of result sets. Would this work for you?
Ah... Display query results, that didn't catch my eye before.
Yes, that would work, might want to be a bit more descriptive with it though. outputQueryResults.
As I've looked at this more, it's actually very problematic in our pipeline. During PR Verify we execute all the migrations against a copy of production in a transaction that is always rolled back. This behavior allows someone to view sensitive data simply by opening a PR that they otherwise wouldn't have access to. I almost wonder if you should change the default to false and make people enable it. Existing users and anyone moving from Community to Pro would not expect this change.