#33509: Add SQL comment to describe deliberately no-op migration operations
------------------------------+--------------------------------------
Reporter: Adam Johnson | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Comment (by Adam Johnson):
I made a PR: https://github.com/django/django/pull/15416 . Not so hard. If
the ticket is accepted I can finish off tests and docs.
It could also be a chance to move the “MIGRATION NOW PERFORMS OPERATION
THAT CANNOT BE WRITTEN AS SQL” comment after the operation header, for
consistency. I think it makes more sense to have the operation header
first, then a comment about its contents afterwards anyway. Otherwise the
"cannot be written as sql..." might be implied to mean the next several
named operations.
--
Ticket URL: <https://code.djangoproject.com/ticket/33509#comment:2>
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.4f4e96516e2d9dcf8f1f7480aacfe2bc%40djangoproject.com.
