Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Updated MySQL to show setting is deprecated #8137

6 changes: 6 additions & 0 deletions src/guides/v2.3/install-gde/prereq/mysql.md
Original file line number Diff line number Diff line change
Expand Up @@ -414,6 +414,12 @@ To configure a MySQL database instance:

If this setting is not enabled, `setup:db:status` will always report that `Declarative Schema is not up to date`.

{:.bs-callout-info}
The `explicit_defaults_for_timestamp` setting is deprecated. This setting controls deprecated TIMESTAMP behaviors that will be removed in a future MySQL release. When those behaviors are removed, the `explicit_defaults_for_timestamp` setting will be removed as well.

{:.bs-callout-warning}
On Magento projects deployed on the Cloud platform, the `explicit_defaults_for_timestamp` setting for MySQL (MariaDB) defaults to *OFF*

{:.ref-header}
Related topics

Expand Down
6 changes: 6 additions & 0 deletions src/guides/v2.4/install-gde/prereq/mysql.md
Original file line number Diff line number Diff line change
Expand Up @@ -182,6 +182,12 @@ To configure a MySQL database instance:

If this setting is not enabled, `setup:db:status` will always report that `Declarative Schema is not up to date`.

{:.bs-callout-info}
The `explicit_defaults_for_timestamp` setting is deprecated. This setting controls deprecated TIMESTAMP behaviors that will be removed in a future MySQL release. When those behaviors are removed, the `explicit_defaults_for_timestamp` setting will be removed as well.

{:.bs-callout-warning}
On Magento projects deployed on the Cloud platform, the `explicit_defaults_for_timestamp` setting for MySQL (MariaDB) defaults to *OFF*

{:.ref-header}
Related topics

Expand Down