#33538: Migrations autodetector change for djangopolymorphicmodel
-------------------------------------+-------------------------------------
Reporter: markp2 | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: 4.0
Severity: Normal | Resolution: invalid
Keywords: Migrations | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
Comment:
> Is there any way to resolve this and not have the migration auto
generated?
Unfortunately no, all auto-generated migrations should contain only no-op
operations so no SQL statements are issued. If you're having trouble
understanding how Django works, see
TicketClosingReasons/UseSupportChannels for ways to get help.
--
Ticket URL: <https://code.djangoproject.com/ticket/33538#comment:1>
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/064.a209b17b86642ff11a845bc0fad4595b%40djangoproject.com.
