2 commits

Author	SHA1	Message	Date
Monty	192427e37d	MDEV-30333 Wrong result with not_null_range_scan and LEFT JOIN with empty table ... There was a bug in JOIN::make_notnull_conds_for_range_scans() when clearing TABLE->tmp_set, which was used to mark fields that could not be null. This function was only used if 'not_null_range_scan=on' is set. The effect was that tmp_set contained a 'random value' and this caused the optimizer to think that some fields could not be null. FLUSH TABLES clears tmp_set and because of this things worked temporarily. Fixed by clearing tmp_set properly.	2023-02-15 13:56:33 +02:00
Michael Widenius	a7abddeffa	Create 'main' test directory and move 't' and 'r' there	2018-03-29 13:59:44 +03:00

Renamed from mysql-test/r/empty_table.result (Browse further)