[Django] #35719: Add support for optimizemigration to output migration with --check

10 views
Skip to first unread message

Django

unread,
Aug 29, 2024, 2:02:55 PM8/29/24
to django-...@googlegroups.com
#35719: Add support for optimizemigration to output migration with --check
------------------------------+---------------------------------------
Reporter: Adam Johnson | Type: New feature
Status: new | Component: Migrations
Version: dev | Severity: Normal
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+---------------------------------------
`makemigrations --check -v 3` outputs the migration source. I’d like
`optimizemigration --check -v 3` to do similar, outputting the migration
source. This could make it easy to compare what optimization does,
especially when optimizing a migration with `RunPython` operations.
--
Ticket URL: <https://code.djangoproject.com/ticket/35719>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Sep 2, 2024, 5:01:26 AM9/2/24
to django-...@googlegroups.com
#35719: Add support for optimizemigration to output migration with --check
------------------------------+--------------------------------------
Reporter: Adam Johnson | Owner: (none)
Type: New feature | Status: closed
Component: Migrations | Version: dev
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Changes (by Sarah Boyce):

* resolution: => wontfix
* status: new => closed

Comment:

Hi Adam, thank you for the ticket
We recommend when requesting new features they are first discussed on the
forum to validate the idea, do you mind opening a discussion and if you
receive some positive feedback that others will also find this useful -
linking that back here and re-opening the ticket?
--
Ticket URL: <https://code.djangoproject.com/ticket/35719#comment:1>
Reply all
Reply to author
Forward
0 new messages