#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 Michel Samia):
regarding step 3: actually sqlite itself probably supports getting number
of unsatisfied constraints for given connection. It should be this call:
https://www.sqlite.org/c3ref/db_status.html with this parameter:
SQLITE_DBSTATUS_DEFERRED_FKS
(https://www.sqlite.org/c3ref/c_dbstatus_options.html). I checked briefly
if this function is exposed to pysqlite but didn't find it there. I'll ask
in the github issue of pysqlite. This would allow us to query sqlite for
fk violations and only if it says that number of fk violations > 0, we
would run our full constraint checking.
--
Ticket URL: <https://code.djangoproject.com/ticket/29928#comment:8>
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.761d8b2d9e1120bc995b944142b3e811%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
