#29928: TestCase doesn't check for foreign key constraints when using sqlite
-------------------------------------+-------------------------------------
Reporter: Michel Samia | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 2.1
Severity: Normal | Resolution:
Keywords: sqlite db foreign | Triage Stage: Accepted
key TestCase |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
I'm not convinced `SQLITE_DBSTATUS_DEFERRED_FKS` would help here, foreign
key constraints would always be deferred from what I understand.
The main issue here is that our implementation of `check_constraints()` is
pretty slow as it performs a ton of introspection queries:
1. 1 query to retrieve all table names
2. 1 query per table to retrieve the PK column name
3. 1 query per foreign key per table to assert foreign data integrity
Given we create a ton of tables for the test suite running this check on
each test teardown is not an option unless we find a way to speedup the
process.
--
Ticket URL: <https://code.djangoproject.com/ticket/29928#comment:10>
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/068.cd11af2d756d2c3c7c4c5580dd097bf8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
