#36170: Running no-op migrations (verbose_name, ...) slow on sqlite
-------------------------------------+-------------------------------------
Reporter: Klaas van Schelven | Owner: Ahmed
Type: | Nassar
Cleanup/optimization | Status: assigned
Component: Migrations | Version: 5.1
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 Ahmed Nassar):
I have Optimized **no-op migration** performance on `SQLite`
- Introduced `must_check_constraints` in `DatabaseSchemaEditor` to track
whether constraints should be checked.
- Ensured that `check_constraints()` is only triggered when SQL statements
are executed.
- Added tests to validate the behavior across different migration
scenarios.
PR: https://github.com/django/django/pull/19278
--
Ticket URL: <https://code.djangoproject.com/ticket/36170#comment:6>
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/01070195a410a871-f39f2020-8ee3-4ef0-84e6-1133d95d9d90-000000%40eu-central-1.amazonses.com.
