#12702: Database exceptions problem in multi-db setups
---------------------------------------------------+------------------------
Reporter: wkornewald | Owner: nobody
Status: new | Milestone: 1.2
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by russellm):
My point is that *none* of the backends raise django.db.IntegrityError -
they raise psycopg.IntegrityError or cx_Oracle.IntegrityError or
MySQLdb.IntegrityError. There isn't a base class to any of these
exceptions, so there isn't any common behavior that you can rely on in the
general case.
However, this problem has become slightly more pointed now that we have
multiple databases. As you pointe out, django.db.DatabaseException points
to the DatabaseException for the default database, which isn't especially
helpful if you're in a multiple database vendor situation. We need to do
something about this for 1.2 - I'm just not sure what. Suggestions
welcome.
--
Ticket URL: <http://code.djangoproject.com/ticket/12702#comment:3>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
