summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorAdrian Holovaty <adrian@holovaty.com>2012-02-03 20:13:16 +0000
committerAdrian Holovaty <adrian@holovaty.com>2012-02-03 20:13:16 +0000
commite2e3d4da0c5056d5899d9604e0d455098be27513 (patch)
tree3a11a8c61f79db6f2f5e9670933529342bf99f5a /docs
parent20dbbcc2643e4983b3cfc85d1ae074ff4e0a6d27 (diff)
Edited releases/1.4.txt changes from [17353]
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17425 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
-rw-r--r--docs/releases/1.4.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/releases/1.4.txt b/docs/releases/1.4.txt
index cb0f01ed7d..fa583ffdb4 100644
--- a/docs/releases/1.4.txt
+++ b/docs/releases/1.4.txt
@@ -773,11 +773,11 @@ object, Django raises an exception.
``MySQLdb``-specific exceptions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-The MySQL backend could raise :class:`MySQLdb.OperationalError`
-when a query triggered an exception. This bug was fixed and
-:class:`django.db.utils.DatabaseError` is now raised instead.
-If you were testing for :class:`MySQLdb.OperationalError`,
-you must update your ``except`` clauses.
+The MySQL backend historically has raised :class:`MySQLdb.OperationalError`
+when a query triggered an exception. We've fixed this bug, and we now raise
+:class:`django.db.utils.DatabaseError` instead. If you were testing for
+:class:`MySQLdb.OperationalError`, you'll need to update your ``except``
+clauses.
Database connection's thread-locality
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~