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

Commit 605ed97

Browse files
authored
Merge pull request #8630 from magento/dobooth-patch-1
Small typo fix in Install Guide
2 parents e8b61b8 + b6a2313 commit 605ed97

File tree

1 file changed

+2
-2
lines changed
  • src/guides/v2.4/install-gde/prereq

1 file changed

+2
-2
lines changed

src/guides/v2.4/install-gde/prereq/mysql.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -167,12 +167,12 @@ To configure a MySQL database instance:
167167

168168
1. In order for MySQL `TIMESTAMP` fields to follow the preferences and composition expected by Magento's declarative schema architecture, the system variable `explicit_defaults_for_timestamp` must be set to `on`.
169169

170-
References;
170+
References:
171171

172172
* [MySQL 5.7](https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_explicit_defaults_for_timestamp)
173173
* [MariaDB](https://mariadb.com/kb/en/server-system-variables/#explicit_defaults_for_timestamp)
174174

175-
If this setting is not enabled, `setup:db:status` will always report that `Declarative Schema is not up to date`.
175+
If this setting is not enabled, `bin/magento setup:db:status` will always report that the `Declarative Schema is not up to date`.
176176

177177
{:.bs-callout-info}
178178
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.

0 commit comments

Comments
 (0)