#1515: Injecting into database exceptions is more portable than copying
exceptions
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: Database wrapper
Version: SVN | Resolution:
Keywords: | Stage: Design decision
needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-----------------------------------+----------------------------------------
Comment (by mtredinnick):
The only thing preventing me from saying this is a really good idea is
whether it's sensible Python practice. Somebody (me?!) needs to do some
research about whether injecting extra base classes like this is frowned
on. I suspect it won't work in general (e.g. C-wrapped classes), but I
don't know.
If we can guarantee it works for all database exceptions, then it's a good
idea.
--
Ticket URL: <http://code.djangoproject.com/ticket/1515#comment:2>
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
-~----------~----~----~----~------~----~------~--~---
