We’ve found that using generate-changelog in version 2.0 strips off the length parameter from nvarchars
( eg an nvarchar(255) ends up in the change log as an nvarchar ), but we don’t appear to have this
issue in version 1.9.5. We’re using an MSSQL2005 database. Is this a known problem, and if so, is there a workaround ?
We think this might have already been reported here: http://liquibase.org/forum/index.php?topic=19.new#new, but this suggests the issue has been fixed in 2.0.