In the yet to be released MySQL 5.6.6 DMR, there has been a change to the restriction of just one TIMESTAMP column with the DEFAULT CURRENT_TIMESTAMP and ON UPDATE CURRENT_TIMESTAMP syntax. It is now possible for any TIMESTAMP to have either column defintion.
More information at http://dev.mysql.com/doc/refman/5.6/en/news-5-6-5.html
I was again reminded why setting SQL_MODE is so important in any new MySQL environment. While performing benchmark tests on parallel backup features with a common InnoDB tablespace and per file tablespace, I inadvertently missed an important step in the data migration.
Read moreIn a recent rant on Why I think SQL_MODE is useless… , I wanted to counteract this statement with why we MUST all use SQL_MODE, even with the inherit flaws.
Read moreIn addition to speaking at RMOUG event in Denver, I also spoke today in Broomfield on “Improving MySQL Performance with Better Indexes”. This presentation included details on : Effective examples of capture SQL via application logging and TCP/IP analysis necessary for identifying the best candidates.
Read more