#22431: TestCase swallows IntegrityError when creating object with invalid
foreign
key
-------------------------------------+-------------------------------------
Reporter: cjerdonek | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.6
Component: Documentation | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
TestCase,IntegrityError,TransactionTestCase,ForeignKey| Patch needs
improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by timo):
* component: Database layer (models, ORM) => Documentation
* type: Bug => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
I would guess switching to immediate constraint checking would have a
performance penalty. It doesn't seem worth it for the majority of cases so
I'd be in favor of simply documenting this. If you want to try to work up
a patch otherwise, we can of course take a look.
--
Ticket URL: <https://code.djangoproject.com/ticket/22431#comment:4>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.999c83a6263bb31fba2b793043abdb24%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
