During db schema creation on 3.3 all tables will be created in varchar

Note regarding fix

This issue has been fixed in Crowd 3.4.3 as well as 3.5.0. However those Crowd versions will only set the correct column types on newly created columns. If upgrading from an affected version (3.3.0-3.4.0) it's important to check for varchar, clob and text columns in the database and manually change them to the appropriate types.

Issue Summary

Prior to 3.3, customers could use our custom SQLServerIntlDialect and tables would be created as nvarchar, instead of MS SQL default varchar.
Starting with Crowd 3.,3 db schema creation process is using liquibase, as a result, the dialect is not respected anymore and tables being created as varchar or converted to varchar during an upgrade.

Environment

Crowd 3.3
Ms SQL

Expected results

When using SQLServerIntlDialect dialect, tables are created with nvarchar columns allowing them to store Unicode characters.

Actual Results

Tables are created with MSSQL default varchar
During an upgrade from earlier versions, if columns were nvarchar, the upgrade will convert them to varchar replacing Unicode characters already stored in the tables in the process.

Workaround

There is no workaround to prevent this, but columns can be manually changed to nvarchar after the upgrade/installation.