Everything, Everything

2020: January February March April
2019: J F M A M J J A S O N D
2018: J F M A M J J A S O N D
2017: J F M A M J J A S O N D
2016: J F M A M J J A S O N D
2015: J F M A M J J A S O N D
2014: J F M A M J J A S O N D
2013: J F M A M J J A S O N D
2012: J F M A M J J A S O N D
2011: J F M A M J J A S O N D
2010: J F M A M J J A S O N D
2009: J F M A M J J A S O N D
2008: J F M A M J J A S O N D
2007: J F M A M J J A S O N D
2006: J F M A M J J A S O N D
2005: J F M A M J J A S O N D
2004: J F M A M J J A S O N D
MySQL show_compatibility_56
Monday 14th September, 2015 15:02 Comments: 0
A rather subtle change has been introduced in MySQL 5.7 that hit me today, but thankfully you can work around this change in behaviour. Oracle have introduced and deprecated the setting "show_compatibility_56" as of MySQL 5.7.6.

show_compatibility_56

The Performance Schema tables are intended to replace the INFORMATION_SCHEMA tables, which are deprecated as of MySQL 5.7.6 and will be removed in a future MySQL release.

This has solved my problem, but developers may have to keep this in mind when they write their software. I'm looking at you, MediaWiki.
© Robert Nicholls 2002-2020
The views and opinions expressed on this site do not represent the views of my employer.
HTML5 / CSS3