Unicode comments that are saved when the table is created are stored as invalid strings.

Discussion of open issues, suggestions and bugs regarding Entity Developer - ORM modeling and code generation tool
Post Reply
ChangHyeon Lee
Posts: 11
Joined: Wed 14 Jun 2017 05:46

Unicode comments that are saved when the table is created are stored as invalid strings.

Post by ChangHyeon Lee » Tue 27 Mar 2018 02:56

I typed the Unicode string in Documentation> Summary of EntityDeveloper.

And I create a table in the database with "Update database from model ...".

Like this...

https://newennetworks-my.sharepoint.com ... w?e=GTxssW

Unicode comments are normal in the above figure.

However, the comments in the generated table are stored as invalid comments.
Like this...

https://newennetworks-my.sharepoint.com ... Q?e=822dkw


If I run the following script directly from dbForge Studio, comments are saved normally.

CREATE TABLE msquarev2.CONFIGS (
`KEY` VARCHAR(255) NOT NULL COMMENT '설정 키',
VALUE VARCHAR(255) NULL COMMENT '설정 값',
PRIMARY KEY (`KEY`)
)
COMMENT '설정 정보 테이블';

Could you fix this problem?

Shalex
Site Admin
Posts: 9543
Joined: Thu 14 Aug 2008 12:44

Re: Unicode comments that are saved when the table is created are stored as invalid strings.

Post by Shalex » Thu 29 Mar 2018 17:20

Please add "Unicode=true;" to the connection string used by Entity Developer (via Database Explorer). Does this fix the issue?

Post Reply