I get charset error from columns defined as TEXT in BDM.

Submitted by msakirkutlu_1359205 on Wed, 09/05/2018 - 15:21
1
0
-1

I am currently running community version 7.7.2 on ubuntu 16.04 server and i defined a column as a text field in bdm because field could be more than 255 char. But when i set that columns as a text it started show charset error. I dont have any such error with string fields.

Corrupted text
Daha �nce google docs �zerinde sekreterden takibettiimiz k1sa kod, cep ve _irket i�i telefon bilgileri bu ortamdan izlensin. G�ncellemeler kolayl1kla tan1ml1 sekreter taraf1ndan yap1ls1n

Thanks in advance

1 answer

Submitted by antoine.mottier on Wed, 09/12/2018 - 10:43
1
0
-1

Are you using UTF-8 encoding for your database? In order to prevent any issue related to encoding all the Bonita components need to work with UTF-8.

You can read the documentation about database configuration here: https://documentation.bonitasoft.com/bonita/7.7/database-configuration#toc5

Comments

Submitted by msakirkutlu_1359205 on Wed, 09/12/2018 - 11:16

Yes, my database using UTF-8 encoding. If i understand it correctly, when a column set as a text, database contains inserted values in a text file and insert a reference to database.

It's not only related to database and also OS language and charset. When i want to create a text file which contains Turkish chars, i am getting exact same charset error. So i decided to change my OS language and tried it again. Well after the changing my OS language things started to a little bit strange. I found a bug in bdm installation process. If you remember i reported a bug about Turkish capital "i" letter bug in bonita designer. Reference number is BS-18008. I get same error when i change my OS langauge to Turkish and tried to install bdm. All my bdm tables which contains "i" letter created again with "İ" letter.
So i had to restore my OS language to English and remove all bdm tables which contains capital "İ" letter, change all text columns to varchar(1500). For now it solved my problem but bug is in there and i will report it.

Permalink
Submitted by antoine.mottier on Wed, 09/12/2018 - 11:23

Can you share with me the output of the following command in a Linux terminal: locale

Also can you let me know which database server you are using?

Permalink
Submitted by msakirkutlu_1359205 on Wed, 09/12/2018 - 11:26

LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

And my database : PostgreSQL 9.3.22 on x86_64-pc-linux-gnu (Ubuntu 9.3.22-1.pgdg16.04+1), compiled by gcc (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609, 64-bit

Permalink
Submitted by antoine.mottier on Wed, 09/19/2018 - 11:33

Further discussion on this issue will happen on the Jira issue.

Permalink
Notifications