cancel
Showing results for 
Search instead for 
Did you mean: 

More than MAX_JOIN_SIZE rows error

former_member672670
Participant
0 Kudos

Hie Guys,

I am getting the following error message - "The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okayState", while parsing objects in UDT 4.1.

The Universe is based on derived tables from a MySQL database. I get the same error message when I Check Syntax for the derived tables. The Universe was working fine before, but all of a sudden I am getting this error. I do not get any errors in the DEV Server. Could anyone please help me identify and resolve this issue? I've attached the snapshot below.

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member4998
Active Contributor
0 Kudos

Hi...


I think error is not related to BO, I suspect it’s related to SQL.

Please check the below workaround was to hardcode it in drupal core :

Mentioned in the below link :

https://drupal.org/node/361967

Go to folder /includes, and find the file : database.mysql.inc

Edit the file :Find this:

/* On MySQL 4.1 and later, force UTF-8 */
if (version_compare(mysql_get_server_info(), '4.1.0', '>=')) {
mysql_query('SET NAMES "utf8"', $connection);
}
return $connection;
}


and add mysql_query('SET SQL_BIG_SELECTS=1 '); so in the end it should look like this :


/* On MySQL 4.1 and later, force UTF-8 */
if (version_compare(mysql_get_server_info(), '4.1.0', '>=')) {
mysql_query('SET NAMES "utf8"', $connection);
}
mysql_query('SET SQL_BIG_SELECTS=1 ');
return $connection;
}

https://drupal.org/node/361967

Also please check the below links.

https://drupal.org/node/1378010

http://coderecho.com/the-select-would-examine-more-than-max_join_size-rows/

https://bugs.launchpad.net/mahara/+bug/1070046

former_member4998
Active Contributor
0 Kudos

Hi.. Is your problem had solve or not?

former_member672670
Participant
0 Kudos

i do not know where to find the file database.mysql.inc. I do not have access to the database.

i added "SET SQL_BIG_SELECTS = 1;"  to the beginning of the SQL query for my derived table, but it throws a  syntax error.