aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSeb Bacon <seb.bacon@gmail.com>2012-01-04 11:29:43 +0000
committerSeb Bacon <seb.bacon@gmail.com>2012-01-04 11:29:43 +0000
commitec18594621d4b13e2820ed475b6a80ef37cd5862 (patch)
treedc882247ca93ce8eb82d87d7d5bd800c99eb2d32
parentbd58c4c90d448f7da9a3b1141af7bbe5cf730126 (diff)
Document why we use SQL_ASCII encoding at mySociety
-rw-r--r--doc/INSTALL.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/INSTALL.md b/doc/INSTALL.md
index 8779f717c..3f794e2fb 100644
--- a/doc/INSTALL.md
+++ b/doc/INSTALL.md
@@ -86,6 +86,12 @@ The following command will set up a user 'foi' with password 'foi':
GRANT ALL PRIVILEGES ON DATABASE foi_test TO foi;
ALTER DATABASE foi_development OWNER TO foi;
ALTER DATABASE foi_test OWNER TO foi;" | psql
+
+We create using the ``SQL_ASCII`` encoding, because in postgres this
+is means "no encoding"; and because we handle and store all kinds of
+data that may not be valid UTF (for example, data originating from
+various broken email clients that's not 8-bit clean), it's safer to be
+able to store *anything*, than reject data at runtime.
# Configure email