You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0)
Build Identifier:
hello, all, i installed monetdb in windows server 2008(64bit) , and installed the odbc for windows( 32bit intalled firstly, and 64bit the next), after insert some Chinese characters, i use oracle biee to show the table data, but biee can't show all the characters, just like below:
0 广ͫ
1 梅
1)monetdb data showed in biee
i also install mysql to test this, the database character set is utf8 too, and biee can show the data correctly:
0 广州
1 梅州
2)mysql data showed in biee
the data showed in command line tool are the same from monetdb and mysql
monetdb command line tool return:
sql>select * from test2;
+------+
| nam |
+======+
| 骞垮窞 |
| 姊呭窞 |
+------+
2 tuples (2.189ms)
mysql commad line tool return:
mysql> select * from test;
+--------+
| nam |
+--------+
| 骞垮窞 |
| 姊呭窞 |
+--------+
2 rows in set (0.00 sec)
Does this mean that: the odbc driver of monetdb has some problems?
the dbvisualizer show the chinese characters correctly through jdbc driver, but biee using monetdb odbc driver can't show all the characters, seems the string is truncated, but with mysql odbc driver, everything is ok.
'骞垮窞' is a utf-8 encoding string for '广州', that means your obiee show the utf string directly, not translate it into gbk or gb2312, maybe you should change your obiee environment to gbk encoding;
I'm lost. I see two sets of (to me) unrelated tables. In the one set I see two rows of 3 glyphs each (the command line interfaces using both mclient and mysql). In the other set I see two rows of 2 glyphs each. What is the relationship between those sets?
Are those two sets different views of the same database table or are they indeed different tables? What are the encodings involved, and what is actually stored in the database? I'd love to see an actual byte sequence of the data in the database. Would it be possible to package up the dbfarm directory into a zip file and either attach that to this bug report or send it directly to me? Best would be if there's nothing else in the database.
You say, "'骞垮窞' is a utf-8 encoding string for '广州'". What exactly do you mean by that? When I copy and paste those strings, I get utf-8 encoded strings for both. One is 9 bytes long, the other 6.
Created attachment 122
dbfarm files and screenshot
here are the dbfarm files and screenshot, i create a schema 'dw', and create a table 'test' with only one column 'nam'(varchar(10)), i inserted some chinese character from dbvisualizer, in the sql command dialog, the chinese characters did not show correctly, but it did inserted, when i executed the select command, the dbvisualizer show the characters correctly, just like '广州' and '梅州', but in obiee, it show the characters not correctly, some characters are missing.
i use windows 7 Chinese Simplified Edition, 64bit
Main issue is "charset problem with the odbc driver for windows" then download the best tutorial from http://screenshotwindows.net and resolve the problem.
The text was updated successfully, but these errors were encountered:
Date: 2012-06-18 11:11:12 +0200
From: liangm <<13802880779>>
To: clients devs <>
Version: 11.9.7 (Apr2012-SP2) [obsolete]
CC: khushikashyap123
Last updated: 2018-10-17 06:59:30 +0200
Comment 17361
Date: 2012-06-18 11:11:12 +0200
From: liangm <<13802880779>>
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0)
Build Identifier:
hello, all, i installed monetdb in windows server 2008(64bit) , and installed the odbc for windows( 32bit intalled firstly, and 64bit the next), after insert some Chinese characters, i use oracle biee to show the table data, but biee can't show all the characters, just like below:
0 广ͫ
1 梅
1)monetdb data showed in biee
i also install mysql to test this, the database character set is utf8 too, and biee can show the data correctly:
0 广州
1 梅州
2)mysql data showed in biee
the data showed in command line tool are the same from monetdb and mysql
monetdb command line tool return:
sql>select * from test2;
+------+
| nam |
+======+
| 骞垮窞 |
| 姊呭窞 |
+------+
2 tuples (2.189ms)
mysql commad line tool return:
mysql> select * from test;
+--------+
| nam |
+--------+
| 骞垮窞 |
| 姊呭窞 |
+--------+
2 rows in set (0.00 sec)
Does this mean that: the odbc driver of monetdb has some problems?
Reproducible: Always
Comment 17373
Date: 2012-06-18 16:54:36 +0200
From: @sjoerdmullender
Can you generate a log file and attach that to the bug report? I'm especially interested in the failing interaction (i.e. using the Oracle biee).
You can see in bug #2910, comment 1, how to do this.
Comment 17375
Date: 2012-06-18 18:04:43 +0200
From: liangm <<13802880779>>
Created attachment 117
logfile
the dbvisualizer show the chinese characters correctly through jdbc driver, but biee using monetdb odbc driver can't show all the characters, seems the string is truncated, but with mysql odbc driver, everything is ok.
Comment 17376
Date: 2012-06-18 18:12:31 +0200
From: liangm <<13802880779>>
Created attachment 118
use_this_odbc_log
Comment 17377
Date: 2012-06-18 18:14:40 +0200
From: liangm <<13802880779>>
Created attachment 119
screen snapshot
Comment 17382
Date: 2012-06-26 09:54:31 +0200
From: @sjoerdmullender
Created attachment 121
screenshot of OBIEE window
I cannot reproduce the problem. When I try to reproduce it in OBIEE I end up with the results that you can see in the attached screen shot.
Comment 17384
Date: 2012-06-26 10:56:56 +0200
From: liangm <<13802880779>>
'骞垮窞' is a utf-8 encoding string for '广州', that means your obiee show the utf string directly, not translate it into gbk or gb2312, maybe you should change your obiee environment to gbk encoding;
Comment 17387
Date: 2012-06-26 15:23:27 +0200
From: @sjoerdmullender
I'm lost. I see two sets of (to me) unrelated tables. In the one set I see two rows of 3 glyphs each (the command line interfaces using both mclient and mysql). In the other set I see two rows of 2 glyphs each. What is the relationship between those sets?
Are those two sets different views of the same database table or are they indeed different tables? What are the encodings involved, and what is actually stored in the database? I'd love to see an actual byte sequence of the data in the database. Would it be possible to package up the dbfarm directory into a zip file and either attach that to this bug report or send it directly to me? Best would be if there's nothing else in the database.
You say, "'骞垮窞' is a utf-8 encoding string for '广州'". What exactly do you mean by that? When I copy and paste those strings, I get utf-8 encoded strings for both. One is 9 bytes long, the other 6.
Comment 17388
Date: 2012-06-27 03:30:42 +0200
From: liangm <<13802880779>>
Created attachment 122
dbfarm files and screenshot
here are the dbfarm files and screenshot, i create a schema 'dw', and create a table 'test' with only one column 'nam'(varchar(10)), i inserted some chinese character from dbvisualizer, in the sql command dialog, the chinese characters did not show correctly, but it did inserted, when i executed the select command, the dbvisualizer show the characters correctly, just like '广州' and '梅州', but in obiee, it show the characters not correctly, some characters are missing.
i use windows 7 Chinese Simplified Edition, 64bit
Comment 17389
Date: 2012-06-27 18:06:37 +0200
From: @sjoerdmullender
Changeset 65609602b082 made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=65609602b082
Changeset description:
Comment 17390
Date: 2012-06-27 19:31:44 +0200
From: @sjoerdmullender
Thanks for the database and the images. I was able to reproduce the problem now, and so was able to find the bug.
Comment 17394
Date: 2012-06-29 12:46:12 +0200
From: @sjoerdmullender
Closing since the bug was fixed.
Comment 17482
Date: 2012-07-17 13:57:42 +0200
From: @grobian
Fix released in Jul2012
Comment 26645
Date: 2018-10-17 06:59:30 +0200
From: khushi <>
Main issue is "charset problem with the odbc driver for windows" then download the best tutorial from http://screenshotwindows.net and resolve the problem.
The text was updated successfully, but these errors were encountered: