use_nationalized_character_data global property is ignored

Description

When use_nationalized_character_data is set to true, national character types are not used.

Environment

None

Activity

Show:
Steve Ebersole
February 15, 2016, 3:41 PM

Going to need a test case showing this. I have tests already showing this works, so need to see the difference.

NareshN
February 16, 2016, 3:15 AM

Added the test file.. varchar is generated instead of nvarchar.

Steve Ebersole
February 16, 2016, 3:09 PM

Gah, silly miss. I missed initializing the "building option" for using nationalized character data from this setting. I will fix that. In the meantime, the API call will fix that. Change your call to build the Metadata to route through MetadataBuilder explicitly and call MetadataBuilder#enableGlobalNationalizedCharacterDataSupport(true). That building option should get initialized from the config setting map, but was not.

Fixed

Assignee

Steve Ebersole

Reporter

NareshN

Fix versions

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Affects versions

Priority

Major
Configure