Re: Strange bug - Heikki Tuuri - com.mysql.lists.bugs

3 messages in com.mysql.lists.bugsRe: Strange bug

From	Sent On	Attachments
Peter Zaitsev	07 Aug 2001 01:54
Sinisa Milivojevic	07 Aug 2001 05:11
Heikki Tuuri	07 Aug 2001 06:47

Subject:	Re: Strange bug
From:	Heikki Tuuri (Heik...@innobase.inet.fi)
Date:	08/07/2001 06:47:08 AM
List:	com.mysql.lists.bugs

Hi!

I think Cal Evans reported 'sort aborted' at the start of July. I do not know the table types he used. Tianlin reported the problem with InnoDB tables. I just tried Tianlin's tables, but was not able to repeat the error. Tianlin said that if you remove ORDER BY, you will get correct results.

If someone can produce a repeatable test case of the error, that would be valuable.

Regards,

Heikki

At 03:11 PM 8/7/01 +0300, you wrote:

Peter Zaitsev writes:

Hello bugs,

I'm using mysql 3.23.39+INNODB but it looks like it there is a problem in queries then one of the tables is INNODB, while other is MYISAM:

mysql> select u.id, concat(u.id,'.',md5(concat(u.login,':',u.pword))) as str -> from counter.users as u, laproviders.user_details as ud where -> ud.user_id=u.id and ud.type&2=2 order by id; ERROR 1028: Sort aborted

mysql> explain select u.id, concat(u.id,'.',md5(concat(u.login,':',u.pword))) as str -> from counter.users as u, laproviders.user_details as ud where -> ud.user_id=u.id and ud.type&2=2 order by id;

+-------+--------+---------------+---------+---------+------+-------+------- ---------+

+-------+--------+---------------+---------+---------+------+-------+------- ---------+

| u | ALL | PRIMARY | NULL | NULL | NULL | 83674 | Using filesort | | ud | eq_ref | PRIMARY | PRIMARY | 4 | u.ID | 1 | where used |

+-------+--------+---------------+---------+---------+------+-------+------- ---------+

2 rows in set (0.00 sec)

The users table is INNODB while user_details is MYISAM.

The problem is the error code 1028 is unknown and the Sort Aborted message is not described anywhere.

I've restarted mysql with new version of 40b (new INNODB) and it seems to work but the question is if this bug is known to be fixed in 40b or it appeared after some time of runtime.

Best regards, Peter mailto:pz...@spylog.ru

Just to clear up a things a bit.

Does it happen only when you mix InnoDB tables with MyISAM tables or it happens with all tables being just InnoDB or just MyISAM ??

There will be an option in 4.0 that will disallow transactional and non-transactional tables in queries.