Difference between revisions of "Full UTF8 support"
Jump to navigation
Jump to search
old>Admin |
m |
||
(One intermediate revision by the same user not shown) | |||
Line 15: | Line 15: | ||
Note an administration profile is needed to complete the operation. | Note an administration profile is needed to complete the operation. | ||
You might also have to update the tomcat server.xml file. | |||
You have to add <code>useBodyEncodingForURI="true"</code> to the connectors. |
Latest revision as of 12:53, 4 October 2024
Special characters causing errors
Problem
The default support for UTF8 is 3 byte.
Using 4 byte UTF content in text areas, can cause errors, that looks like
java.sql.SQLException: Incorrect string value: '\xC2\x96 Z. ...' for column 'NOTES' at row 1
Solution
Update the database to full UTF8 support using the following command
main?command=dk.p2e.blanket.codeunit.common.PageConvertDatabaseToUTF8
Note an administration profile is needed to complete the operation.
You might also have to update the tomcat server.xml file.
You have to add useBodyEncodingForURI="true"
to the connectors.