By ComputerX on

Hi,

I have just moved a Drupal based site from a server running Drupal 6.22, Apache version 2.2.21, PHP version 5.2.9, and MySQL version 4.1.22-standard to one running Drupal 6.22, Apache version 2.2.2, PHP version 5.2.17, and MySQL version 5.1.56. MySQL has changed from version 4 to version 5. This is a dedicated server and I can do with it as I like.

I am getting the following errors:

Warning: The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET SQL_MAX_JOIN_SIZE=# if the SELECT is okay query: SELECT filename FROM drup_system WHERE name = 'user' AND type = 'module' in /home/www/public_html/includes/database.mysql.inc on line 135

Warning: The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET SQL_MAX_JOIN_SIZE=# if the SELECT is okay query: SELECT src FROM drup_url_alias WHERE dst = 'admin' AND language IN('en', '') ORDER BY language DESC, pid DESC in /home/www/public_html/includes/database.mysql.inc on line 135

I have found several posts, such as this one, that propose a fix, but I don't know where to apply it.

Is there a universal fix that does not require tracking down offending queries?

If not, how do I find what is generating the error?

Many Thanks,

Dan

⋅ Categories: Drupal 6.x

Comments

ComputerX’s picture

ComputerX commented

To answer an obvious question, here is the statement that is referenced in the error.

  else {
    // Indicate to drupal_error_handler that this is a database error.
    ${DB_ERROR} = TRUE;
    trigger_error(check_plain(mysql_error($active_db) ."\nquery: ". $query), E_USER_WARNING);
    return FALSE;

Thanks in advance,

Dan