#31398: multiple_database.tests.AuthTestCase doesn't flush the default database
if
transactions aren't supported.
------------------------------+---------------------------------------
Reporter: Tim Graham | Owner: Nick Michas
Type: Bug | Status: assigned
Component: Core (Other) | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+---------------------------------------
Comment (by Nick Michas):
Replying to [comment:17 Tim Graham]:
> Hi Nick, your proposal to change the behavior of flush isn't the
solution I expected. I believe the underlying problem is that the test
writes to a table that shouldn't exist because of the router. Instead of
changing the behavior of flush to account for a broken test, the test
should be fixed.
Thanks for the feedback Tim, I wasn't sure if the proposed change would be
the correct one.
I will take another look in the test tomorrow and try to understand the
problem as my current understanding is that it purposely tries to write to
this table.
--
Ticket URL: <https://code.djangoproject.com/ticket/31398#comment:18>
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/0107019da0af7fa4-a7a51146-8745-47af-a878-c12ee0321021-000000%40eu-central-1.amazonses.com.
