Status: Released (View Workflow)
- With the current documentation.sql script for MySQL to create the new documentation tables the columns NAME, DIRECTORY and PATH are created with CHARACTER SET latin1. This results in garbled entries for Text containing characters which are not in the latin1 character set.
- With the current documentation.sql script for MS SQL Server to create the new documentation tables the columns NAME, DIRECTORY and PATH are created as VARCHAR. Additionally the hibernate configuration file for the reporting DB tables is configured with sendStringParametersAsUnicode=false; in the connection url property.
- For MySQL the columns have to be modified to allow unicode characters to be able to store text with characters which are not in the latin1 character set.
- For MS SQL Server the columns have to be modified from VARCHAR to NVARCHAR to allow unicode characters to be stored.
- For MS SQL Server the hibernate configuration file for the reporting DB tables has to be updated to remove the sendStringParametersAsUnicode=false; part in the connection url.
- For compatibility reasons, the setup does not remove the sendStringParametersAsUnicode=false; in the case of MSSQL.
- This has to be removed manually, but the setup will not add the removed sendStringParametersAsUnicode=false; again during an update.
- is functional requirement for
JOC-650 A document should be imported successfully even it has arbitrary UTF-8 letters in its filename