* user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE variable_name IN ('character_set_database', 'character_set_results', 'coll' at line 1 query: SHOW VARIABLES WHERE variable_name IN ('character_set_database', 'character_set_results', 'collation_connection', 'collation_database', 'collation_server', 'have_dynamic_loading', 'have_innodb', 'have_isam', 'have_query_cache', 'have_raid', 'max_connections', 'query_cache_size', 'query_cache_type') in /opt/www/drupal-5.1.int.thatsbj.com/includes/database.mysql.inc on line 172.
* user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE variable_name IN ('Qcache_free_memory', 'Qcache_hits', 'Qcache_not_cached'' at line 1 query: SHOW STATUS WHERE variable_name IN ('Qcache_free_memory', 'Qcache_hits', 'Qcache_not_cached', 'Qcache_queries_in_cache', 'Max_used_connections', 'Threads_running', 'Threads_cached', 'Threads_connected', 'Threads_created') in /opt/www/drupal-5.1.int.thatsbj.com/includes/database.mysql.inc on line 172.

From my quick look at the MySQL docs page I don't see where it's possible to use a WHERE clause here. The examples mention using LIKE clauses....

Comments

nancydru’s picture

Hmm, it works fine on my site, and I know at least one other user who has used it with those new changes.

What version of MySql are you using?

nancydru’s picture

Title: query errors when collecting MySQL data » Query Errors when collecting MySQL data
Assigned: Unassigned » nancydru
jaydub’s picture

4.1.20

nancydru’s picture

Hmm, I'm using 5.something. I wonder what my servers are running.

nancydru’s picture

One of my live servers is on 4.1.22 and I see the same problem. Now to try to find out how, or what minimum level this works at.

nancydru’s picture

Status: Active » Fixed

Okay, I just committed a change. It should be available in a few hours. It makes some "ugly" queries, but it works on both 4.1.22 and 5.0.27.

nancydru’s picture

From MySql manual for 3.23, 4.0, and 4.1

End of Product Lifecycle.
Active development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

You might want to ask your host to move to a supported version... I did.

Anonymous’s picture

Status: Fixed » Closed (fixed)