Closed Bug 774855 Opened 12 years ago Closed 12 years ago

Django DB exception changed

Categories

(support.mozilla.org :: General, defect)

Product:
support.mozilla.org
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
2012Q4

People

(Reporter: jsocol, Assigned: rrosario)

References

Details

(Whiteboard: u=dev c=general p=0 s=2012.24) 

If we're on 1.4 now, or when we are, we need to pay attention to the release notes[1] especially around places where Django used to throw MySQLdb-specific OperationError, and now throws a generic DatabaseError. E.g. read_only_mode and middleware.

[1] https://docs.djangoproject.com/en/dev/releases/1.4/#mysqldb-specific-exceptions
We're still using 1.3, but I tacked this onto the 1.4 upgrade bug.
Whiteboard: u=dev c=general p=
Assignee: nobody → rrosario
Target Milestone: --- → 2012Q4
Whiteboard: u=dev c=general p= → u=dev c=general p=0 s=2012.24
Landed and deployed:

https://github.com/mozilla/kitsune/commit/b99c68c6ccea418fc730717294c9a83df6cab781
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.