Page 1 of 1

Russian language problems

Posted: Tue May 04, 2021 11:03 am
by MohamadAli

we recently migrated from mysql to sql server DB. When testing the new DB, all russian characters now appear as ???.

SQL Sever DB Collation is set to "Latin1_General_100_CI_AS" because when I tried to set it to "Latin1_General_100_CI_AS_UTF8", openkm failed to create database.

If I try to change "NBS_NAME" column's type to nvarchar (saw on google that this might solve the issue), sql server doesnt allow me to do it, and tells me that I should drop the table and create it again. Is this safe to do? I dont have a problem losing data because we still in test phase.

Can you guide me about the topic please?

Re: Russian language problems

Posted: Thu May 06, 2021 7:17 pm
by jllort
Always backup database before doing this kind of actions. Also you can play with restored database either the production one.

I ignore if Latin1_General_100_CI_AS is the right locale or should you choose another, a good test will be create a fresh openkm and check choosen locale ( creating a folder with special characters should be enought ).

From my point of view SQL Server seems have reinvented the wheel with so many locales, Oracle, PostgreSQL, MariaDB, MySQL use standard UTF-8 concept -> the same happens with windows that do not use UTF-8 and use their own ISO-XXXX