Age | Commit message (Collapse) | Author |
|
backend. Switch yamltest's default database configuration to sqlite3.
MySQL still has character set issues, which are almost certainly to do
with the communication channel rather than the database tables. It's
possible that one of the newer DB API drivers for MySQL fixes this,
might be worth trying one of them at some point (see the "MySQL notes"
discussion of MySQL DB API drivers in the Django documentation).
svn path=/branches/tk705/; revision=6149
|
|
else.
svn path=/branches/tk705/; revision=6147
|
|
incorrectly coded UTF-8 in BLOB fields holding ASN.1 DER data. This
is wrong in so many ways that I don't even know where to start, but,
bottom line, forcing Latin1 here is just making MySQL 5.6+ revert to
the behavior in MySQL 5.5.
This is just a workaround. The real solution is probably to switch to
an SQL engine that's not quite such a kludge tower.
svn path=/branches/tk705/; revision=6146
|
|
svn path=/branches/tk705/; revision=6123
|
|
warnings: Django 1.8 has a really obscure way of saying "Please don't
import your models into your apps' __init__.py files, thanks."
svn path=/branches/tk705/; revision=6101
|
|
incomprehensible advance depreciation warnings for Django 1.9.
svn path=/branches/tk705/; revision=6100
|
|
particular programs (see #713).
svn path=/branches/tk705/; revision=6098
|