hazza/jupyterhub
1
0
Fork 0
mirror of https://github.com/jupyterhub/jupyterhub.git synced 2025-10-18 15:33:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

database docs: fix formatting

Browse Source
This commit is contained in:
Chico Venancio
2018-06-08 13:09:09 -03:00
parent c75eddb730
commit 91a67bf580
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/source/reference/database.md
View File

@@ -52,11 +52,11 @@ additional configuration required for MySQL that is not needed for PostgreSQL.
from the hub will be idle for longer than most connections. This behavior from the hub will be idle for longer than most connections. This behavior
will lead to frustrating 'the connection has gone away' errors from will lead to frustrating 'the connection has gone away' errors from
sqlalchemy if `pool_recycle` is not set. sqlalchemy if `pool_recycle` is not set.
- If you use utf8mb4 collation with MySQL earlier than 5.7.7 or MariaDB earlier - If you use `utf8mb4` collation with MySQL earlier than 5.7.7 or MariaDB
than 10.2.1 you may get an '1709, Index column size too large' error. To fix earlier than 10.2.1 you may get an `1709, Index column size too large` error.
this you need to set 'innodb_large_prefix' to enabled and To fix this you need to set `innodb_large_prefix` to enabled and
'innodb_file_format' to 'Barracuda' to allow for the index sizes jupyterhub `innodb_file_format` to `Barracuda` to allow for the index sizes jupyterhub
uses. 'row_format' will be set to 'DYNAMIC' as long as those options are set uses. `row_format` will be set to `DYNAMIC` as long as those options are set
correctly. Later versions of MariaDB and MySQL should set these values by correctly. Later versions of MariaDB and MySQL should set these values by
default, as well as have a default DYNAMIC row_format and pose no trouble to default, as well as have a default `DYNAMIC` `row_format` and pose no trouble
users. to users.