diff and generateChangeLog results are incorrect when a view causes an error on MySQL
Description
Environment
MySQL 5.6.23, Liquibase 3.5.1 running in Windows 7
Activity
Show:
Nathan Voxland September 2, 2016 at 2:15 PM
Yes, that is the problem. When the view is invalid we don't get a list of columns. I'll have to add logic to try to handle that case
If a view is broken - for example if you rename a table that the view references - then diff and generateChangeLog both return incorrect results. All of the columns in the tables are ignored - I'm guessing that the view issue causes Liquibase to fail before parsing out the columns but it does not cause Liquibase to fail with an exception so you get a changelog or diff report but it is incorrect and all of the columns are missing.