[boydell]

boydell wrote on Jun 4 2007, 04:28 AM:

This is still a problem in community version 6. I can get to happen every time with many different queries, on many different computers. It is not a problem with the clipboard, because the same resultsets copy just fine from toad.

Bump. Still a problem with community v6.07 on every computer I have installed it on, in both win xp and linux through wine.

[boydell]

peterlaursen wrote on Jan 10 2007, 11:59 AM:

It is now fixed in the development tree.

We plan to release 5.23 beta1 by beginning/mid next week with the fix for this.

Actually we did delete the old clipboard content from memory, but doing this and allocating the buffer for the new content was done in the wrong order.

This is still a problem in community version 6. I can get to happen every time with many different queries, on many different computers. It is not a problem with the clipboard, because the same resultsets copy just fine from toad.

I can't seem to nail down the limit. The number of rows possible change with one query to the next, although it seems to hover around 10,000. And the total bytes copied seems to also vary from one query to the next. And sometimes the amount I can copy from a specific result set is consistent. and sometimes it varies.

Here is a script to create a table to test the problem.

drop table if exists clipboard;

create table clipboard (

field1 int(10) unsigned not null auto_increment,

field2 varchar(255) not null default '',

primary key (field1)

) engine=MyIsam default charset=utf8;

DELIMITER $$

DROP PROCEDURE IF EXISTS `test_clipboard`$$

CREATE PROCEDURE `test_clipboard`()

BEGIN

declare cnt int default 0;

while cnt < 20000 do insert into clipboard (field2) values ('Here is some text for the field'); set cnt = cnt + 1; end while; END$$ DELIMITER ; call test_clipboard(); select * from clipboard limit 12000;

[Author]

Posts