You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Victor Romero (Jira)" <ji...@apache.org> on 2025/03/03 20:33:00 UTC
[jira] [Comment Edited] (FINERACT-2195) UTF8 issue for Interest Rate Chart
[ https://issues.apache.org/jira/browse/FINERACT-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17932083#comment-17932083 ]
Victor Romero edited comment on FINERACT-2195 at 3/3/25 8:32 PM:
-----------------------------------------------------------------
[~adamsaghy] before sending the PR I have review tha the Maria DB configuration have been proeperly set:
[mysqld]
collation-server=utf8mb4_unicode_ci
init-connect='SET NAMES utf8mb4'
character-set-server=utf8mb4
And make sure that the JDBC connection is enforcing the unicode:
"&useUnicode=true&characterEncoding=UTF-8"
Finally I have verified that the databsae and its tables have been created using utf8mb4_unicode_ci, seems that by default the MariaDB is casting the number to string using the utf8mb4_general_ci collation.
Maybe another approach could be used...
was (Author: victorromero):
Before sending the PR I have review tha the Maria DB configuration have been proeperly set:
[mysqld]
collation-server=utf8mb4_unicode_ci
init-connect='SET NAMES utf8mb4'
character-set-server=utf8mb4
And make sure that the JDBC connection is enforcing the unicode:
"&useUnicode=true&characterEncoding=UTF-8"
Finally I have verified that the databsae and its tables have been created using utf8mb4_unicode_ci, seems that by default the MariaDB is casting the number to string using the utf8mb4_general_ci collation.
{{}}
{{}}
> UTF8 issue for Interest Rate Chart
> -----------------------------------
>
> Key: FINERACT-2195
> URL: https://issues.apache.org/jira/browse/FINERACT-2195
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Victor Romero
> Priority: Major
> Attachments: Interest_rate_issue.txt
>
>
> When using Maria DB the SQL Query cannot retrieve deposit products because whend doing cast to char it tries to use UTF-8 General instead of UTF-8Unicode
--
This message was sent by Atlassian Jira
(v8.20.10#820010)