Setting the wchar attribute for data source connections

In NexJ CRM version 8.4, the unicode attribute for data source connections was replaced with the wchar attribute. Previously, you could use the unicode property to define character encoding for a data source connection by specifying the property in the connections or environment file.

Note: This is typically a developer task that is performed in NexJ Studio by a person with access to the model. A deployment specialist may also modify the wchar attribute.

If you are upgrading from NexJ CRM version 8.3 or earlier and have specified the unicode property, you must set the wchar attribute to the same value. For example, if you have explicitly set unicode="true" then you must now set wchar="true".

If you have not previously specified a unicode property, then you do not need to define the wchar attribute. The default values provide optimal performance settings for each database type.

Note: You can specify a new value for the wchar attribute by adding the attribute to the environment file. However, do not add the attribute unless it is required. Note that MySQL and PostgresSQL do not support wide characters.

The following table lists the default wchar attribute values by database type.


Database type	Default wchar value
MSSQL, DB2, and Sybase	True
Oracle	False
MySql and PostgreSQL	Null