Page 1 of 1

5.90.0.59 Has broken String Saving of Easten Code Page

Posted: Fri 02 Jul 2010 10:15
by Justmade
Maybe due to your "fixing" of dumping, saving string to MySQL using Easten Code Page introduce some new problem.

For example, in a TMyQuery using a table with a varchar field, when I input Traditional Chinese 紅白藍袋, it will become 紅\白藍\袋 after saved to database and then refreshed.

I had checked with MySQL Monitor and it is still without the '\ in the MySQL Monitor Parameters.

When I install back to .58, the problem disappear.

I am using Delphi 7 in XP with latest versions of MySQL 5.1.

Thanks in advance for your assistance.

Posted: Fri 02 Jul 2010 15:36
by Dimon
I can not reproduce the problem.
When does the problem appear - on backing up or on restoring data?
Try to compose a complete sample to demonstrate the problem and send it to dmitryg*devart*com.

Posted: Sat 03 Jul 2010 04:21
by Justmade
no, it is not in the DUMP, it is on the normal use.

as I stated above, just use any table using big5 varchar field.

then use TMyQuery and a TDBEdit.

The adding of \ happen when saving input to mysql.

Notes that not all Chinese Char would cause this. Maybe only when the first byte of the Char is within some range.

As this only happen in the latest version, I think maybe your DUMP fix modify some shared code that format the string field which also applied to normal TMyQuery.

Posted: Wed 07 Jul 2010 13:27
by Justmade
I hoped this will be fixed in the next release.

Thanks.

Posted: Thu 29 Jul 2010 08:19
by geekman1024
I'm having the same problem, any Chinese characters I input using TCRDBGrid will have a \ inserted between 2 Chinese characters. This is rather irritating, since it will cause my clients calling in to complain about the extra \ inserted in their data. i.e. Their organization/company name will become unusable when they use my application to print company letter head.

Any suggestion to get rid of the extra \ in the data, except downgrading to older revision?

Posted: Thu 29 Jul 2010 13:56
by Dimon
Thank you for information. We have reproduced this problem and fixed it. This fix will be included in the next MyDAC build.