Mercurial > kallithea
annotate docs/changelog.rst @ 5619:6353b5e87091
ini: specify utf8 for sample MySQL connection strings
By default, the MySQL stack will store unicode as UTF-8 encoded data in string
fields, thus without using any unicode capabilities in the database.
As described in
http://docs.sqlalchemy.org/en/latest/dialects/mysql.html#mysql-unicode , set
charset=utf8 to actually put unicode in the database.
Existing databases that already store utf8 in the database should keep using
the old url.
This will only support 16 bit code points, but utf8mb4 will double the key size
and make them too big for MySQL.
author | Mads Kiilerich <madski@unity3d.com> |
---|---|
date | Tue, 05 Jan 2016 16:30:11 +0100 |
parents | fbbe80e3322b |
children |
rev | line source |
---|---|
585 | 1 .. _changelog: |
2 | |
2095 | 3 ========= |
585 | 4 Changelog |
5 ========= | |
6 | |
5425
5ae8e644aa88
docs: spelling, grammar, content and typography
Søren Løvborg <sorenl@unity3d.com>
parents:
4177
diff
changeset
|
7 Kallithea project doesn't keep its changelog here. We refer you to our `Mercurial logs`__. |
2041
d533249e7d55
docs updates for release
Marcin Kuzminski <marcin@python-works.com>
parents:
2020
diff
changeset
|
8 |
5433
fbbe80e3322b
docs: consistent spacing around headings
Mads Kiilerich <madski@unity3d.com>
parents:
5425
diff
changeset
|
9 |
5425
5ae8e644aa88
docs: spelling, grammar, content and typography
Søren Løvborg <sorenl@unity3d.com>
parents:
4177
diff
changeset
|
10 .. __: https://kallithea-scm.org/repos/kallithea/changelog |