Comment 1 for bug 1516010

The cause is that MySQL used to only support implicit timestamp default value, which is not according to the SQL spec. When this was fixed, it was decided to keep the old behavior for historical reasons, but add a deprecation warning.

Adding the suggested value to the config would remove the warning, but we'd be changing the default behavior of the server.