On Sun, 2007-08-19 at 05:19 -0700, ludvig.ericson wrote: > Well actually, I see implementation leakage in the API here. > > Does it make sense that the Django ORM raises SQLite3 exceptions? I > wouldn't want _to try to try to_ catch either of all integrity > exceptions. > > Perhaps something like 'django.db.IntegrityError' or so.
We already have that. You can catch django.db.IntegrityError and it will work (same goes for DatabaseError). The exception class still reports its own name as sqlite3.IntegrityError or whatever it is, but that's just an unavoidable Python feature (a consequence of using references). Regards, Malcolm -- On the other hand, you have different fingers. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
