[wp-trac] Re: [WordPress Trac] #3792: MySQL version checking

[WordPress Trac]

#3792: MySQL version checking
---------------------------------------+------------------------------------
 Reporter:  Ozh                        |        Owner:  pishmishy
     Type:  enhancement                |       Status:  assigned 
 Priority:  low                        |    Milestone:  2.4      
Component:  Optimization               |      Version:           
 Severity:  normal                     |   Resolution:           
 Keywords:  mysql version needs-patch  |  
---------------------------------------+------------------------------------
Changes (by pishmishy):

  * owner:  ryan => pishmishy
  * status:  new => assigned

Comment:

 I'm not sure that caching the result is such a great idea, there's good
 way to determine when we should refresh the value stored in the cache.
 Refreshing in upgrade.php seems an odd idea as I've never upgraded MySQL
 at the same time as I do WordPress upgrades.

 Do many plugins really ''need'' to check the version of MySQL being used?
 Authors should really expect to be as conservative as WordPress is when it
 comes to SQL queries. I appreciate that's a rather ideal view, but it
 should result in better plugins.

 Do those plugins need to check the version of MySQL every time a part of
 the plugin is invoked? That's the only scenario in which I can see the
 number of queries being a problem.

 Recommend that the ticket is resolved as wontfix, '''or'''
 mysql_get_server_info() is used without caching, '''or''' the same
 function is wrapped into the wpdb class.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/3792#comment:10>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software