, 2002 3:16 AM
Heikki Subject: Re: InnoDB, possible bug?
I am using mysql 4.0.1-alpha on Linux 2.4.18, the info you requested is:
select count(*) from newsentries10 where playerid=28575 and type=2;
+--+
| count(*) |
+--+
| 4218 |
+--+
1 row in set (13.81 sec)
mysql
: InnoDB, possible bug?
Hello,
I've just switched to InnoDB table from myISAM and it's been running
pretty
smoothly except on this SQL statement it doesn't use any indexes when
there
are, and therefore is very slow.
mysql explain select
pn.timestamp,ne.viewpoint,pn.id,pn.type,ne.type
(0.00 sec)
Andrei Cojocaru
[EMAIL PROTECTED]
- Original Message -
From: Heikki Tuuri [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, May 21, 2002 12:40 PM
Subject: Re: InnoDB, possible bug?
Andrei,
how many rows in ne satisfy
(1) ne.playerid=28575,
(2) ne.type=2?
What
and latest news on InnoDB
- Original Message -
From: Andrei Cojocaru [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]; Mysql List
[EMAIL PROTECTED]
Sent: Wednesday, May 22, 2002 3:16 AM
Subject: Re: InnoDB, possible bug?
I am using mysql 4.0.1-alpha on Linux 2.4.18, the info you requested
Hello,
I've just switched to InnoDB table from myISAM and it's been running pretty
smoothly except on this SQL statement it doesn't use any indexes when there
are, and therefore is very slow.
mysql explain select
pn.timestamp,ne.viewpoint,pn.id,pn.type,ne.type,ne.newsid,ne.hidestamp from
