From ab576328f0cf8d6d38c2cc6d0fee5de50a4c99a3 Mon Sep 17 00:00:00 2001
From: "kostja@oak.local" <>
Date: Mon, 15 Sep 2003 22:21:39 +0400
Subject: Fixed bug in the optimiser for FULL TABLE SCAN case: to estimate
 correctly cost of full table scan we should take into account rows read and
 skipped on each iteration.

---
 mysql-test/r/select_safe.result | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'mysql-test/r/select_safe.result')

diff --git a/mysql-test/r/select_safe.result b/mysql-test/r/select_safe.result
index c4e5984d360..1ee1368d029 100644
--- a/mysql-test/r/select_safe.result
+++ b/mysql-test/r/select_safe.result
@@ -70,7 +70,7 @@ insert into t1 values (null,"a"),(null,"a"),(null,"a"),(null,"a"),(null,"a"),(nu
 explain select STRAIGHT_JOIN * from t1,t1 as t2 where t1.b=t2.b;
 table	type	possible_keys	key	key_len	ref	rows	Extra
 t1	ALL	b	NULL	NULL	NULL	21	
-t2	ALL	b	NULL	NULL	NULL	16	Using where
+t2	ref	b	b	21	t1.b	6	Using where
 set MAX_SEEKS_FOR_KEY=1;
 explain select STRAIGHT_JOIN * from t1,t1 as t2 where t1.b=t2.b;
 table	type	possible_keys	key	key_len	ref	rows	Extra
-- 
cgit v1.2.1