summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStephen Finucane <stephen@that.guru>2021-02-20 15:12:53 +0000
committerStephen Finucane <stephen@that.guru>2021-02-20 15:14:50 +0000
commit576647e9e084d60b3c67dd56c47f1510a671f297 (patch)
tree3f74b9e180205ba3dcc2394f75980efb154c57fe
parent5fe02b6a7444b40f705d1efe33e70a9a9ef36e0a (diff)
downloadpatchwork-576647e9e084d60b3c67dd56c47f1510a671f297.tar
patchwork-576647e9e084d60b3c67dd56c47f1510a671f297.tar.gz
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 <stephen@that.guru> Closes: #393
-rw-r--r--docs/deployment/installation.rst11
1 files changed, 11 insertions, 0 deletions
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
---------