This comes from an issue that I worked on recently, wherein a
customer reported that their application was working fine under
stock MySQL 5.6 but producing erroneous results when they tried
running it on Amazon RDS 5.6. They had a table which, on the
working server, contained two TIMESTAMP columns, one which
defaulted to CURRENT_TIMESTAMP and the other which defaulted to
’0000-00-00 00:00:00′, like so:

MySQL 5.6 upgrades are in full swing these days and knowing how
to safely upgrade from MySQL 5.5 to 5.6 is important. When
upgrading a replication environment, it’s important that you can
build a migration plan that safely allows for your upgrade with
minimal risk — rollback is often a very important component to
this.

For many people this means upgrading slaves first and then the
master. The strategy of an older master replicating to a
newer slave is well known and has been …

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.