Bug Report: MSSQL nvarchar losing length in 2.0, but works in 1.9.5


  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.


Tim Ash

Are you using the latest 2.0 RC5 ?


We are using the RC 5 from the download page, we are not using the latest build from trunk as we cannot access that page for some reason.

Yes, the build server appears to be offline.  It isn’t a server I managed and am suspicious it will be gone for good :frowning:

I’ll take a look at your issue and let you know what I find.


any report on this