- March 2021
- February 2021
- October 2020
- June 2020
- May 2020
- October 2019
- June 2019
- September 2018
- May 2018
- December 2017
- April 2017
- June 2016
- February 2016
- November 2015
- January 2015
- August 2014
- July 2014
- May 2014
- March 2014
- February 2014
- January 2014
- November 2013
- August 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- December 2012
- November 2012
- September 2012
- June 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- September 2011
- July 2011
- June 2011
- May 2011
- March 2011
- January 2011
- October 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- September 2009
- July 2009
- June 2009
- May 2009
- March 2009
- September 2008
- April 2008
- December 2007
- June 2007
- June 2005
- September 2004
- May 2002
- October 2001
- August 2001
2013-05-23: Tip: Getting rid of the warning "The column name 'start' is a MySQL reserved keyword."
Version 4 and later of popular database management tool phpMyAdmin "helpfully" displays warnings when a column name in a database conflicts with a reserved word in MySQL. This may or may not be an actual problem. If you are in the habit of enclosing table names in your SQL queries in `backticks`, it shouldn't be a problem at all. For others, it may depend on the actual column name. In the example provided below, "start" and "end" can safely be SELECTed unquoted, whereas "group" needs the backticks. At any rate, having the warnings show up the whole time rather than just at table creation time is annoying. Here's how to disable them.
As phpMyAdmin 4 is new, it took some searching before I found how to disable it. Suppressing these warnings can be done by adding a single line to your config.inc.php:
<?php$cfg['ReservedWordDisableWarning'] = true;?>
That's all there is to it.
Comments
No comments, yet...
Post a comment