diff options
| author | Damien Lespiau <damien.lespiau@intel.com> | 2014-08-31 01:02:37 +0100 |
|---|---|---|
| committer | Jeremy Kerr <jk@ozlabs.org> | 2014-09-07 20:07:40 +0800 |
| commit | e4f09a3605ea8f1efeeb6cae1fdf3bba9dbd412c (patch) | |
| tree | 620c71f7afecd1dfcbb6cb0a097052da451b658d /apps/settings.py | |
| parent | ad5fce448df4d6f604de3b2275cbeb3d4f2f3817 (diff) | |
| download | patchwork-e4f09a3605ea8f1efeeb6cae1fdf3bba9dbd412c.tar.bz2 patchwork-e4f09a3605ea8f1efeeb6cae1fdf3bba9dbd412c.tar.xz | |
INSTALL: Sprinkle a few UTF-8 in the mysql documentation
When not specifying the charset/collation, I managed to create a latin1
database where all strings were encoded in latin1. That's really not
ideal. Adding 'CHARACTER SET utf8' when creating the DB fixes it. Then:
$ ./manage.py syncdb
will correctly create tables with UTF-8 encoded rows.
However, for some reason, when django creates the test tables, that
default, DB wide, encoding is not respected and one needs to provide an
additional TEST_CHARSET entry in the config dictionary.
Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
Diffstat (limited to 'apps/settings.py')
0 files changed, 0 insertions, 0 deletions