Bug 364762

Summary: Invalid mysql configuration option table_cache
Product: [Applications] digikam Reporter: Steven Robbins <steve>
Component: Database-MysqlAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, metzpinguin, swatilodha27
Priority: NOR    
Version First Reported In: 5.0.0   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
URL: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808729
Latest Commit: http://commits.kde.org/digikam/ceea763c6dd60cd151ee9e855a7dc14b41befecc Version Fixed/Implemented In: 5.0.0
Sentry Crash Report:

Description Steven Robbins 2016-06-25 23:49:25 UTC 
As reported by a Debian user: mysql-global.conf uses an unsupported option that causes the db server to not start at all.  

In MySQL 5.1.3, the variable table_cache was renamed to table_open_cache.  For several releases, both names worked, but starting in 5.6, it seems the older name is completely removed.  Quoting https://bugs.mysql.com/bug.php?id=68315 :


This change was documneted in 5.1.3 change log - http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-3.html
and http://dev.mysql.com/doc/refman/5.1/en/upgrading-from-previous-series.html

See, Incompatible Change: Renamed the table_cache system variable to table_open_cache. Any scripts that refer to table_cache should be updated to use the new name. 

Also, table_cache is the old name of table_open_cache before MySQL 5.1.3. From 5.1.3 on, use table_open_cache instead. 

http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_table_cache



Reproducible: Always
Comment 1 caulier.gilles 2016-06-26 04:43:02 UTC 
Swati,

This option must be fixed in configurations files before 5.0.0 release.

Also, there is an important question : It's the same changes in config option name for Oracle Mysql and MariaDb ?

Gilles Caulier
Comment 2 swatilodha27 2016-06-29 17:53:28 UTC 
Configuration file changed.

And yes, table_open_cache is valid for both Oracle MySQL and Maria DB.