MySQL Bugs: #6724: Query Browser becomes sluggish/nonresponsive on datatype with many linefeeds

Bug #6724	Query Browser becomes sluggish/nonresponsive on datatype with many linefeeds
Submitted:	19 Nov 2004 18:03	Modified:	20 Nov 2004 23:41
Reporter:	Chris Price	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S1 (Critical)
Version:		OS:	Windows (Windows XP Pro)
Assigned to:		CPU Architecture:	Any

Description:
I have an InnoDB table with a column of TEXT datatype. I inserted a 64k string of x's. 

From MySQL Administrator, I clicked on the table name, and column and chose "Edit table Data". This launches MySQL Query browser. 

I was able to browse this with the query browser succesfully. 

I then tried a 64k string of "x\n" (x followed by newline character). MySQL Query Browser became sluggish/nonresponsive to the point of being unusable.

I also tried with a 64k string of "xxxxxxx\n" (7 x followed by newline), with the same result.

How to repeat:
Create table with TEXT datatype
Create a string with a large # of newline character, ie: (PERL)
    my $data    ="xxxxxxx\n" x 8192;
Insert into database;

Launch Query Browser directly and select * from table, or through Administrator, click on edit table data.

Observe query browser come to a screaching halt

Using:
P4 3.2Ghz Hyper Thread, 2GB RAM, WinXP Pro

Suggested fix:
Unknown

Which version you are using for MA and QB, because with MA 1.0.14
Edit Table Data is grayed and QB 1.1.1 not presents that behavior.

Thanks.

I am using MySql Administrator 1.0.14. The edit table data will be grayed out if you dont have Query Browser Installed. I have QB installed. Mine is NOT grayed out.  

It doesnt matter what version of MA you are using, since Query Browser will have this behavior when launched stand alone as well.  

I can reproduce it every time. 64k string of x is no problem 64k string with x\n will reproduce the behavior.

I am using QB 1.0.8 Beta, I just noticed there is 1.1.1 gamma available. I will test it out and reply back.

Update: 1.1.1 Gamma does not show this behavior. 

As you reported, it also does not allow you to launch the Query Browser from Administrator. Im not sure if this is a bug or an intentional feature removal, but It definitely is a detriment. Being able to launch QB from MA was a great feature.

I downloaded and installed 1.0.8 beta only a few days before this bug report, I was not aware that 1.1.1 was available.

I am closing this issue because QB 1.1.1 not shows that issue
and the grayed issue of MA belongs to bug:

http://bugs.mysql.com/bug.php?id=6470

and even in closed status should be handled there.

Thanks you for the bug report.