Exception when running update statement with utf8 encoding

Discussion of open issues, suggestions and bugs regarding database management and administration tools for MySQL
Post Reply
Justmade
Posts: 108
Joined: Sat 16 Aug 2008 03:51

Exception when running update statement with utf8 encoding

Post by Justmade » Tue 28 Dec 2010 03:43

Below is the script generated by your data comparison sync.

Code: Select all

-- Script was generated by Devart dbForge Studio for MySQL, Version 4.50.314.0
-- Script date 2010/12/28 11:26:18
-- Source server version: 5.1.49-community
-- Source connection string: User Id=root;Host=localhost;Port=3308;Ping Interval=240;Character Set=AUTO;
-- Target server version: 5.1.49-community
-- Target connection string: User Id=root;Host=localhost;Port=3307;Character Set=utf8;
-- Run this script against ebsapp_escape_new to synchronize it with ebsapp
-- Please backup your target database before running this script

SET NAMES 'utf8';
USE ebsapp_escape_new;

--
-- Disable foreign keys
--
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;

--
-- Updating data of table langstr
--
UPDATE langstr SET tis = 'เอกสาร Refresh | อ่านข้ที่คุณเปิดเฟรชครั้งล่าสุด'
 WHERE Str = 'ACT_DOCREFRESH_H';

--
-- Enable foreign keys
--
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
FYI, the field content is thai language.

When executing, it generate the below error :

輸出位元組緩衝區太小,無法包含已編碼的資料,編碼方式 'Unicode (UTF-8)' 後援 'System.Text.EncoderReplacementFallback'。
參數名稱: bytes

As it is Chinese, I would try to translate it as follow :
The buffer for output bytes is too small. Cannot include the encoded data. Encoding : 'Unicode (UTF-8)'

Support: 'System.Text.EncoderReplacementFallback' Variable Name : bytes

If copy the update statement to be execute alone, the error is the same.

If copy the update statement to other mysql clients (tested : SQLyog, MySQL Front, MySQL Query Browser) to execuate, there is no error.

Thanks in advance for your help.

Alexz
Devart Team
Posts: 165
Joined: Wed 10 Aug 2005 08:30

Post by Alexz » Tue 28 Dec 2010 14:16

We've reproduced this problem. We are invesitgating it now and we'll inform you about the results of the investigation.

Alexz
Devart Team
Posts: 165
Joined: Wed 10 Aug 2005 08:30

Post by Alexz » Wed 29 Dec 2010 12:15

We fixed this problem. The fix will be included in the next build of dbForge Studio for MySQL v4.50. We'll inform you when the new build is available for download.

Justmade
Posts: 108
Joined: Sat 16 Aug 2008 03:51

Post by Justmade » Wed 29 Dec 2010 13:24

Thanks you very much.

Alexz
Devart Team
Posts: 165
Joined: Wed 10 Aug 2005 08:30

Post by Alexz » Wed 05 Jan 2011 15:47

The new build of dbForge Studio for MySQL, v4.50.316 is available for download:
http://www.devart.com/dbforge/mysql/stu ... nload.html.

Post Reply