In 4.0, we moved the SQL logging back to FINE level from INFO https://github.com/liquibase/liquibase/issues/1501
- Do you agree or disagree that SQL should be logged at FINE level, and why?
- Do you see value in having a liquibase-level configuration flag to control the log level vs. configuring your logging, and why?
- If you rely on seeing the SQL ran by liquibase during an operation, what are your use cases for wanting that?
I’m especially interested in 3 because I think the overall pushback against the move back to FINE level is actually because there is needed functionality around tracking what was ran that we should improve in general.
Is it better SQL reporting you are looking for? Are you interested in both read and write SQL, or just “what sql changed the database” reporting? Is it more for troubleshooting failures if the happen? Is it just to avoid having to call both updateSql and update as part of your build job, or is there more to it than that?
Let us know here or in the issue.