#31275: Optimize MariaDB/MySQL sql_flush
-------------------------------------+-------------------------------------
Reporter: Adam (Chainz) | Owner: Masashi
Johnson | SHIBATA
Type: | Status: assigned
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
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 Adam (Chainz) Johnson):
> I decided to guide the patch submitter towards avoiding these queries
and suggesting the use of `TransactionTestCase.reset_sequences` instead
while documenting the behaviour changed in Django 3.1 and that this
feature should be explicitly enabled to achieve this previously implicit
reset.
Very sensible. I forget about this option!
> In summary projects that will benefits from this patch would benefit way
more by defining `available_apps` on their tests.
Yes indeed, although it can be tedious to define and keep correct.
--
Ticket URL: <https://code.djangoproject.com/ticket/31275#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 on the web visit
https://groups.google.com/d/msgid/django-updates/068.959b3484ebaa41dbdc59615108d46a63%40djangoproject.com.
