#3450: Make IntegrityError available from django.db -----------------------+---------------------------------------------------- Reporter: enlight | Owner: adrian Status: new | Component: Database wrapper Version: SVN | Keywords: Stage: Unreviewed | Has_patch: 1 -----------------------+---------------------------------------------------- This is related to ticket #3083, however the issue I'd like to address is just a subset of that ticket, so I figured it's best to create a separate ticket. The attached patch will allow developers to import IntegrityError from django.db thus avoiding a dependency on any specific db module. I mentioned the rationale for this patch in [http://groups.google.de/group/ django-users/browse_thread/thread/0357be5fcc49e4bc/ this thread] on django-users. I have tested the changes on the postgresql and postgresql_psycopg2 backends, and I've looked at api/source for the oracle, mysql, ado_mssql and sqlite3 db modules recommended for use with the other backends. From what I could gather they all provide an IntegrityError as specified by the [http://www.python.org/dev/peps/pep-0249/ Python DB-API 2.0]... still would be best if someone actually tested all those backends :)
-- Ticket URL: <http://code.djangoproject.com/ticket/3450> Django Code <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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-updates?hl=en -~----------~----~----~----~------~----~------~--~---
