Feature #9712
ensure that the language and encoding options in use across the current customer base are properly supported
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:
History
#1 Updated by Greg Shah over 1 year ago
As found in #9699, some customers may be setup with invalid combinations of language and codepage. We need a list of the languages supported and the codepages supported. Based on that, we should ensure that we have orthogonal support for all of those combinations.
This should be done for both H2 (_temp) and for the standard permanent databases (PostgreSQL, MariaDB and soon, SQLServer).
Finally, we need documentation on how these are to be used properly.