Encoding issue for commit messages

Hi everybody. I have an issue with encoding. Commit messages look like:

BE-127 ???????? ????? ????????: implemented.

Where do I have to confiure encoding? Is smth with my OS?
In VCS roots I haven't found any encoding configurations.

---

Russian location and language are installed.
TeamCity Professional 8.0.5 (build 27692)
Windows Server 2012 R2 Standard English.

10 comments
Comment actions Permalink

What databas engine do you use?

0
Comment actions Permalink

The most probably some settings are incorrect.
Please double check that the tables in the database are created with the right character set and collation.

0
Comment actions Permalink

Thank you Pavel and Leonid. You were right. The problem lays in the DB.
Collation is SQL_Latin1_General_CP1_CI_AS. So the problem was in the column types. Changing type from varchar to nvarchar of the vcs_history.description everything worked fine.
Thanks guys!

0
Comment actions Permalink

Hello Artiom,

If you change a collation of one column you can get a problem with upgrade to a new version. In order to avoid future problems, all varchar columns of all tables must have the same collation.

And, in particular for MS SQL, collations of all varchar columns must be exactly same as the default database (not server) collation.

0
Comment actions Permalink

Hi Leonid,
so what do I have to do in this case to get my lovely russian characters look pretier?
Cuz I don't want to have problems in the future and don't want to have them now with ? characters.

0
Comment actions Permalink

so, let's say I will migrate to new DB. Will I have problems with upgrades as you described before?
May be you have misunderstood me: I didn't have collation - I have changed only type of the column from varchar to nvarchar. Cuz collation seems to be fine or I am wrong? (SQL_Latin1_General_CP1_CI_AS)

0
Comment actions Permalink

Hello Artiom,

during the migrate operation there should be no collation related problem.

Don't forget to specify the right defasult collation for the new database before migrating.

> Will I have problems with upgrades as you described before?

No, because all character columns get the same character set and collation.

> May be you have misunderstood me: I didn't have collation - I have changed only type of the column from varchar to nvarchar.

The nvarchar type means another character set.

0
Comment actions Permalink

Thank you Leonid.

0

Please sign in to leave a comment.