Sqlyog Crashes When Trying Show Table Data

[vygi]

I am using SQLyog 5.0 BETA 4 on German Windows XP Professional.

SQLyog permanently crashes when I try to look at data from this table, even when it's empty:

CREATE TABLE `icdrs` (

`carrier_id` tinyint(3) unsigned NOT NULL default '0',

`cdrs_id` int(10) unsigned NOT NULL default '0',

`clone_nr` tinyint(1) unsigned NOT NULL default '0',

`is_call` tinyint(1) unsigned NOT NULL default '0',

`a_number` varchar(22) binary default NULL,

`olo` tinyint(3) unsigned default NULL,

`b_number` varchar(30) binary default NULL,

`start_date_time` datetime NOT NULL default '0000-00-00 00:00:00',

`duration` smallint(5) unsigned NOT NULL default '0',

`duration_orig` smallint(5) unsigned NOT NULL default '0',

`class` enum('Peak','Off-Peak','none') NOT NULL default 'none',

`service_id` smallint(5) unsigned NOT NULL default '0',

`network` enum('INT','NAT','MOB','none') NOT NULL default 'none',

`route` varchar(7) binary NOT NULL default '',

`poi` enum('HAMB','HANN','BERL','MUNC','STUT','FRAN','DUSS','NURN') default NULL,

`zone_id` int(10) unsigned NOT NULL default '0',

`price_id` int(10) unsigned NOT NULL default '0',

`amount` float NOT NULL default '0',

`istatus` tinyint(3) unsigned NOT NULL default '0',

`bill_id` int(10) unsigned NOT NULL default '0',

`time_stamp` timestamp(14) NOT NULL,

PRIMARY KEY (`carrier_id`,`cdrs_id`,`clone_nr`),

KEY `start_date_time` (`start_date_time`),

KEY `istatus` (`carrier_id`,`service_id`,`price_id`,`istatus`),

KEY `zoning` (`carrier_id`,`start_date_time`,`network`,`istatus`),

KEY `cdrs_id` (`cdrs_id`)

) TYPE=MyISAM MAX_ROWS=1000000000 DELAY_KEY_WRITE=1

“SELECT * FROM icdrs LIMIT 100” works, click on “Table Data” tab crashes SQLyog.

Dump file attached.

[adarsh]

Hello,

We are not able to reproduce here.

Please attach the table structure with some sample data.

Thanks

Adarsh

[peterlaursen]

Not reproducable here either on a Danish Vista (and an empty table).

I think we will need to find out if it is data related. Can you reproduce a crash too with an empty table?

[peterlaursen]

OK .. I was just informed by a test engineer in B'lore that the crash can be reprocued when connected to MySQL 4.0 or 3.x – not higher versions. Can you confirm the MySQL version to be 4.0 or lower in your case?

[adarsh]

Hi,

Thank you for reporting.

Issue is confirmed and fixed in development tree.

Thanks

Adarsh

[vygi]

Yes, it happens with MySQL 4.

Is there a chance to get a fixed version soon?

Because I can't use this SQLyog with our older server….

[peterlaursen]

It is fixed in both the 5.x and 6.x development tree now.

Are you asking for a 5.x or 6.x build? We can give a 5.31 'not-releeased' and hope to release 6.0 beta 5 tomorrow.

Is it community/trial/enterprise you need?

[vygi]

peterlaursen wrote on May 10 2007, 08:26 AM:

It is fixed in both the 5.x and 6.x development tree now.

Are you asking for a 5.x or 6.x build? We can give a 5.31 'not-releeased' and hope to release 6.0 beta 5 tomorrow.

Is it community/trial/enterprise you need?

I did not have any problems with previous 5.x versions and none of my workmates have any issues with it but I'm using 6.0 beta 4 at the moment. So no need for any special 5.31, I will wait until tomorrow and install the bets 5 then. Thanks!

[Author]

Posts