This forum topic seems to specifically address a question I have been asked by management. Our project adopted Liquibase release 2.0.5 about 6 months ago and we have been successfully using it since. One aspect of Liquibase that has been puzzling is the lack of feedback that Liquibase provides when it runs SQL. Our project is running against Oracle 11.2.0.4. I did a test today of what was in log file after running Liquibase UPDATE with loglevel of DEBUG. The SQL in files listed in changelogs is displayed in log file several times, but there is no feedback provided for number of rows updated, number of rows deleted, number of rows inserted, etc. That feedback would seem to be very basic information to provide in logfiles that are supposed to have detailed information.
Had a few questions:
1. What is general reason that SQL execution result feedback is not normally provided ? Should be available at DEBUG level of logging for sure.
2. SQL commands get executed and feedback is provided initially as to what happened. Where is the feedback getting stripped away since it is not provided ?
3. Are there any changes planned for future Liquibase releases that would display SQL execution result feedback ? If not can there be a new loglevel for FEEDBACK that will list only the SQL statements actually run and the results of them running ?
4. What is meant by NVoxland comment "Data about the number of rows affected and other forecasting style analytics gets beyond what Liquibase is trying to do..." ? Does this comment mean that providing SQL execution result feedback is out of scope for Liquibase ?
Any replies to any questions above would be helpful for me to explain to others the topic.
Had a few questions:
1. What is general reason that SQL execution result feedback is not normally provided ? Should be available at DEBUG level of logging for sure.
2. SQL commands get executed and feedback is provided initially as to what happened. Where is the feedback getting stripped away since it is not provided ?
3. Are there any changes planned for future Liquibase releases that would display SQL execution result feedback ? If not can there be a new loglevel for FEEDBACK that will list only the SQL statements actually run and the results of them running ?
4. What is meant by NVoxland comment "Data about the number of rows affected and other forecasting style analytics gets beyond what Liquibase is trying to do..." ? Does this comment mean that providing SQL execution result feedback is out of scope for Liquibase ?
Any replies to any questions above would be helpful for me to explain to others the topic.