On Tue, 2003-03-18 at 21:38, [EMAIL PROTECTED] wrote:
> Description:
>
> Hello Peter,
>
> Have you explained to Heikki this problem?
> Have you fixed it?
>
> Please, tell me about it.
>
Dear Rafarife,
This problem is qualified as wrong optimizer plan selection.
Happily yo
Description:
Hello Peter,
Have you explained to Heikki this problem?
Have you fixed it?
Please, tell me about it.
Regards,
Rafa
How-To-Repeat:
Select ... from giros ...
Fix:
-
Synopsis:optimizer bug in the index used by mysql/Inno
Description:
Hello Peter,
I have sent to ftp://support.mysql.com/pub/mysql/secret the table definition
and data (Giros.txt) in a compressed file named Giros.zip so you can
invetigate it.
You can see the following queries:
SELECT TIPO,DOC,NRE
FROM GIROS
WHERE (GIROS.TIPO
Description:
Hello Alexander,
You wrote:
>From EXPLAIN result output you can do only opposite conclusion: With InnoDB MySQL
>chooses
>to use Index TipoFeVCod for which it expects to match 9417 rows. This is about twice
>less
>rows than expected with PRIMARY key in second explain
Hello,
[EMAIL PROTECTED] wrote:
Description:
Hello,
I am working with mysql/InnoDb 4.0.11 under Windows 2000.
I have the following table:
Time: 0.20 secs.
Explain:
table type possible_keys keykey_len ref rows Extra
GIROS range PRI
Description:
Hello,
I am working with mysql/InnoDb 4.0.11 under Windows 2000.
I have the following table:
CREATE TABLE `giros` (
`Doc` varchar(10) NOT NULL default '',
`Tipo` char(1) NOT NULL default '',
`NRe` varchar(5) NOT NULL default '',
`FoP` char(2) N
