MySQL Bugs: #25519: bug on bidi character in IE

Bug #25519	bug on bidi character in IE
Submitted:	10 Jan 2007 7:35	Modified:	10 Jan 2007 10:10
Reporter:	dones mark	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Errors	Severity:	S2 (Serious)
Version:	5.0	OS:	Windows (winxp)
Assigned to:		CPU Architecture:	Any
Tags:	ansi, ASCII, bidi, character, illegal character

Description:
when i paste a character, which i haven't yet identified the byte code, MYSQL returns data too long for field. the character is a LTR character. I can send an rtf file of the character at your request. please email me.

I use eclipse, tomcat 5, connector-j, jdk1.5, struts

How to repeat:
a character bidi type but i cant paste it here. i can send an RTF file if you request.

two characters before this. open it with msword.

Attachment: check-5.rtf (application/msword, text), 5.94 KiB.

ive created an rtf capable textArea or editor and save it's contents to a field.

Thank you for the report.

Please provide output of statements SHOW CREATE TABLE table_you_try_to_insert_bidi_character, SHOW VARIABLES LIKE '%char%' and SHOW VARIABLES LIKE '%coll%'

here is the procedure

Attachment: procedure.txt (text/plain), 1.48 KiB.

i placed the file procedure.txt

heres the error SQLエラー
01004(0):com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'v_body' at row 1

I can not repeat issue using modified procedure you provided.

Which exact version of MySQL do you use?

according to my research, multibyte characters have problems on sql is it right? i  the code was not mine but i was asked to debug. i still haven't got the whole picture yet so i can only give you that procedure. the v_body in that procedure contains text for a certain length.

the code injects tagged data from a "web rich text file editor" which converts formatted text. 

e.g. <span ..... mso-bidi ..... charset-family=>THE CHARACTER</span>

that whole text will be saved to database. now mysql reads it as an overflow?

thank you for your concern

But bug database is place to only hold information of bugs found in MySQL product. I can not repeat the problem using information you provided and have no answer to the questions I asked in previous comments.

So I close report as "Can't repeat". But if you think cause of your problem is MySQL and you use last MySQL, answer my questions and don't hesistate to reopen the bug report.