Bug #256 False ERROR 1104 - ... Set option sql_big_selects
Submitted: 8 Apr 2003 17:46 Modified: 8 Apr 2003 23:08
Reporter: gogman Email Updates:
Status: Closed Impact on me:
Category:MySQLCC Severity:S3 (Non-critical)
Version:mysql 4.1 mysqlcc 9.1 beta OS:Windows (windows xp)
Assigned to: CPU Architecture:Any

[8 Apr 2003 17:46] gogman
Installed MySQL 4.1 alpha. This was an upgrade from MySQL 4.0.
I ran a test query in MySQL Control Center 0.9.1 beta and recieved the following error.

ERROR 1104: The SELECT would examine too many records and probably take a very long time. Check your WHERE and use SET OPTION SQL_BIG_SELECTS=1 if the SELECT is ok.

(1) set option sql_big_selects=1; makes no difference
(2) set-variable	= max_join_size=4294967295; makes no difference
(3) tested using mysql cmd line - no errors (returned proper number of rows
(4) in all test cases I used a Limit 10 in the select statement.
(5) tested my application against these databases (php) - no errors

Since both cmd line mysql and php, executing the same type of queries to the same database do not produce the error, we may assume the MySQL Control Center may be at fault. This only occured when I upgraded to MySQL 4.1 from 4.0.


How to repeat:
(1) using MySQL Control Center 0.9.1 beta query 1m row db on mysql 4.1.
[8 Apr 2003 23:08] Indrek Siitan
This is a known issue of 0.9.1 and has been fixed in 0.9.2.

To fix this meanwhile, edit your server connection and in the "MySQL Options" tab, set a reasonable value for "Automatically limit SELECT queries to" and set the value for "Maximum Join Size" to 1000000.