#31398: multiple_database.tests.AuthTestCase doesn't flush the default database
if
transactions aren't supported.
------------------------------+------------------------------------
Reporter: Tim Graham | Owner: (none)
Type: Bug | Status: new
Component: Core (Other) | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Comment (by Lakshya Prasad):
I investigated this issue and it appears to be already resolved in the
current development version of Django.
The `sql_flush()` function now uses
`connection.introspection.table_names()` instead of
`django_table_names()`, which ensures that all tables are flushed
regardless of database router restrictions.
I verified this by running the `multiple_database` tests and the full test
suite, and no issues were observed.
Please let me know if any further action is needed.
--
Ticket URL: <https://code.djangoproject.com/ticket/31398#comment:11>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019d021e8d99-3c7141b3-2cf1-4f44-9861-da7e1a1b76d3-000000%40eu-central-1.amazonses.com.
