Malcolm Tredinnick e94d293504 There are some variations in the printed names of exceptions between Oracle and ... other database backends, but the exception classes should still be the same. This commit changes the way the tests check for specific database errors to be more portable between implementations. It's possible these tests will still fail if, e.g., Oracle doesn't raise IntegrityError (but raises DatabaseError) when we except it to, but we can cross that bridge if and when it appears. git-svn-id: http://code.djangoproject.com/svn/django/trunk@8450 bcc190cf-cafb-0310-a4f2-bffc1f526a37		2008-08-20 18:50:06 +00:00
..
__init__.py	Added the ability to force an SQL insert (or force an update) via a model's	2008-08-09 17:19:23 +00:00
models.py	There are some variations in the printed names of exceptions between Oracle and	2008-08-20 18:50:06 +00:00