From 576647e9e084d60b3c67dd56c47f1510a671f297 Mon Sep 17 00:00:00 2001 From: Stephen Finucane Date: Sat, 20 Feb 2021 15:12:53 +0000 Subject: docs: Note UTF-8 requirements for databases MySQL 5.3 defaulted to 'latin1' encoding, meaning users would need to explicitly configure their databases to use 'utf8'. Call this out. Signed-off-by: Stephen Finucane Closes: #393 --- docs/deployment/installation.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'docs') diff --git a/docs/deployment/installation.rst b/docs/deployment/installation.rst index 6681002..348af0e 100644 --- a/docs/deployment/installation.rst +++ b/docs/deployment/installation.rst @@ -126,6 +126,17 @@ done later. __ https://www.postgresql.org/docs/10/static/auth-methods.html#AUTH-PEER +.. note:: + + As noted in the `Django documentation`__, Django expects databases to be + configured with an encoding of UTF-8 or UTF-16. If using MySQL, you may + need to configure this this explicitly as older versions defaulted to + `latin1` encoding. Refer to the `MySQL documentation`__ for more + information. + + __ https://docs.djangoproject.com/en/3.1/ref/unicode/ + __ https://dev.mysql.com/doc/refman/en/charset.html + Patchwork --------- -- cgit v1.2.3