A new topic, 'Bug Report: MSSQL nvarchar losing length in 2.0, but works in
1.9.5', has been made on a board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=638.new#new
The text of the topic is shown below:
Hi,
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.
Cheers,
Tim Ash
Unsubscribe to new topics from this board by clicking here:
http://liquibase.org/forum/index.php?action=notifyboard;board=1.0
Regards,
The Liquibase Community Forum Team.
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Liquibase-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/liquibase-user
