test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Edited releases/1.4.txt changes from [17353] 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@17425 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2012-02-03 20:13:16 +00:00
parent 20dbbcc264
commit e2e3d4da0c
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/releases/1.4.txt
View File

@ -773,11 +773,11 @@ object, Django raises an exception.
``MySQLdb``-specific exceptions ``MySQLdb``-specific exceptions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The MySQL backend could raise :class:`MySQLdb.OperationalError` The MySQL backend historically has raised :class:`MySQLdb.OperationalError`
when a query triggered an exception. This bug was fixed and when a query triggered an exception. We've fixed this bug, and we now raise
:class:`django.db.utils.DatabaseError` is now raised instead. :class:`django.db.utils.DatabaseError` instead. If you were testing for
If you were testing for :class:`MySQLdb.OperationalError`, :class:`MySQLdb.OperationalError`, you'll need to update your ``except``
you must update your ``except`` clauses. clauses.
Database connection's thread-locality Database connection's thread-locality
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~