#31275: Optimize MariaDB/MySQL sql_flush
-------------------------------------+-------------------------------------
Reporter: Adam (Chainz) | Owner: Masashi
Johnson | SHIBATA
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"89032876f427a77ab4de26493190280377567d1c" 89032876]:
{{{
#!CommitTicketReference repository=""
revision="89032876f427a77ab4de26493190280377567d1c"
Fixed #31275 -- Optimized sql_flush() without resetting sequences on
MySQL.
Co-Authored-By: Simon Charette <[email protected]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31275#comment:13>
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.b3dd32af10a6ef2acd2a53f310c2caad%40djangoproject.com.
