mirror of
https://github.com/silverstripe/silverstripe-framework
synced 2024-10-22 14:05:37 +02:00
DOC Apply suggested typos fixes
Co-authored-by: Michal Kleiner <mk@011.nz>
This commit is contained in:
parent
235ebe3c3c
commit
be623349ed
@ -59,7 +59,7 @@ see `MySQLDatabase::$sql_mode` for more details.) This setting is only available
|
||||
### MySQL/MariaDB Int width in schema
|
||||
|
||||
MySQL 8.0.17 stopped reporting the width attribute for integers while MariaDB did not change its behaviour.
|
||||
This results in constant rebuilding the schema when MySQLSchemaManager expects a field to look like i.e.
|
||||
This results in constant rebuilding of the schema when MySQLSchemaManager expects a field to look like e.g.
|
||||
`INT(8)` and MySQL server reports it simply as `INT`. MySQLSchemaManager has been updated to detect the MySQL
|
||||
server implementation and act accordingly. In cases when auto-detection fails, you can force the desired behaviour like this:
|
||||
```yml
|
||||
|
@ -251,7 +251,7 @@ It's highly recommended that existing Silverstripe CMS installation using `Swift
|
||||
|
||||
### MySQL/MariaDB Int width in schema
|
||||
MySQL 8.0.17 stopped reporting the width attribute for integers while MariaDB did not change its behaviour.
|
||||
This results in constant rebuilding the schema when MySQLSchemaManager expects a field to look like i.e.
|
||||
This results in constant rebuilding of the schema when MySQLSchemaManager expects a field to look like e.g.
|
||||
`INT(8)` and MySQL server reports it simply as `INT`. MySQLSchemaManager has been updated to detect the MySQL
|
||||
server implementation and act accordingly. In cases when auto-detection fails, you can force the desired behaviour like this:
|
||||
```yml
|
||||
|
Loading…
Reference in New Issue
Block a user