#35040: Migrations Not Affecting The DB With Existing DATA
----------------------------+--------------------------------------
Reporter: msinankk | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 4.2
Severity: Normal | Resolution: needsinfo
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 Mariusz Felisiak):
* status: new => closed
* resolution: => needsinfo
Comment:
Hi, I don't think you've explained the issue in enough detail to confirm a
bug in Django. TBH, I don't understand what exactly you are trying to
report, but I'm pretty sure that you should first check
TicketClosingReasons/UseSupportChannels for ways to get help and use
support channels. You can reopen the ticket if you will debug your issue
and provide details about why and where Django is at fault.
--
Ticket URL: <https://code.djangoproject.com/ticket/35040#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/0107018c6c48cd6e-dc35a8c7-0019-4c38-9070-0b3d6e9ffa7f-000000%40eu-central-1.amazonses.com.
