Devart Forums

MyDAC 5.9.60
Delphi 2010

1. When Set Options' quotename and completeinsert, the field name of insert statement is not quoted

2. utf8 problem has never fixed yet.
I had read the serveral issues of TMyDump and utf8 in the forum and do my own testing and find that the issue had not yet fixed.

I create a simple utf8 table with 3 string fields : latin1, big5, gbk
CREATE TABLE `testunicode` (
`latin1` varchar(50) DEFAULT NULL,
`big5` varchar(50) DEFAULT NULL,
`gbk` varchar(50) DEFAULT NULL
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

There is only 1 record.

dbForge export to script as follow (correct) :
INSERT INTO testunicode VALUES
('E B S S y s t e m', '永 富 商 業 系 統', '永 富 商 业 系 统');

When using TMyDump with no setting of encoding :
INSERT INTO testunicode VALUES
('E B S S y s t e m', '? ? ? ? ? ?', '? ? ? ? ? ?');

When using TMyDump with encoding utf8 useunicode true:
INSERT INTO testunicode VALUES
('E B S S y s t e m', '永 富 商 業 系 統', '永 富 商 ? 系 ?');
(The char not in my system encoding (big5) become ?)

When using TMyDump with encoding utf8 useunicode false:
INSERT INTO testunicode VALUES
('E B S S y s t e m', '瘞?撖???璆?蝟?蝯?, '瘞?撖???銝?蝟?蝏?);

Finally, when using text field instead of varchar, even the useunicode = true mode generate the same rubbish as useunicode = false.

The recommended useunicode false mode generate rubbish even without ending quote and so generate error on restoring.

I had see that when using BackupToFile, it use ansi format so I tried to just use backup (To TMyDump.SQL) and then showmessage it but the result is the same.

Please let me know if this problem will be dealt with.

If it is fixed, then I will order subscription renewal and if it is not to be dealt with in the immediate next version, I had to find other way of dealing my backup need.

Thanks in advance for your response.

Hello,

1. We have fixed this problem. This fix will be included in the next MyDAC build.
2. I cannot reproduce this problem. Please specify the exact code page used on your machine.

Thank you for your response.

I am using Window 7, with non-unicode Language set to Chinese (Traditional, Hong Kong SAR)

As I am using Delphi 2010 with Unicode, and setting the mysql database encoding to utf8, I think the local code page should not be a big different?

Also, I tried dbForge for MySQL (Professional 4.50.311) as well as SQLyog Community v8.61 and they all export that table correctly.

If you prefer, I can sent the output files to you.

I see that the other applications had generate utf-8 encoding text file which TMyDump.BackupToFile create Ansi text file, which is impossible to contain correct unicode text except own's machine code page text.

I think it is quite a fact that Ansi Text output is impossible to handle text out of the system code page setting.

So, are you going to deal with this problem? I do not want to waste time waiting if this issue is never goner to be fixed.

Thanks.

Justmade wrote:I see that the other applications had generate utf-8 encoding text file which TMyDump.BackupToFile create Ansi text file, which is impossible to contain correct unicode text except own's machine code page text.

Thank you for information. We have reproduced this problem and fixed it. This fix will be included in the next MyDAC build.

Dimon wrote: Thank you for information. We have reproduced this problem and fixed it. This fix will be included in the next MyDAC build.

Thank you, we would make a purchase of an upgrade to source code version and await your new build. With source code, maybe we can make some hotfix ourselves faster and let your know more info if we encounter any new issues.

May I ask when the next version is expected to come out? or should I email support to ask for getting the new relevant sources file (I had bought the source code version) to recompile myself?

The next MyDAC build will be released in the course of this week.