#35040: Migrations Not Affecting The DB With Existing DATA
--------------------------------------+------------------------
Reporter: msinankk | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 4.2
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 |
--------------------------------------+------------------------
**The Case**\\
* I have a Django project without running any migration (cz migrations
folder on my git ignore)
* I Replaced the DB(sqlite) with my DB with the data
* Note: In the project I have a model or a field that are new and not
affected the db yet, So here there are no initial migrations file.
* I Run Makemigrations command
* The initial migrations files are generated
* When check the initial migrations file there showing the an effected
model is also created in the operation list.
* I run migrate
* When I try to access the model geting error called no such table/ column
**Currently How We Fix**\\
* Currently we fix this issue by manually comment/remove the un-applied
operation item from the list and re-run the Makemigration and migrate then
it should be fixed
--
Ticket URL: <https://code.djangoproject.com/ticket/35040>
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/0107018c6bfb8444-bcd3176a-98ec-4941-bd95-d867aa7f4a0f-000000%40eu-central-1.amazonses.com.
