[Django] #25100: cant migrate contenttype with django 1.8 when new table is created
Django
-----------------------------------+----------------------------------
Reporter: sachinvettithanam | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Keywords: contentype migration
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+----------------------------------
* Project Build on django 1.4.10
* Database - postgresql (which got large amount data)
Steps to Reproduce issues
1. Upgraded to django 1.8.*
2. Create a new table
3. executing makemigrations works fine
4. when we migrate, migrations works and gives ok response then followed
by
"Error creating new content types. Please make sure contenttypes "
RuntimeError: Error creating new content types. Please make sure
contenttypes is migrated before trying to migrate apps individually.
5. Then try to access this table from admin it gives responce
Error creating new content types. Please make sure contenttypes is
migrated before trying to migrate apps individually.
6. tried migrate contenttype - nothing changes
7. Downgraded to django 1.7 , and executing migration for contenttype
works and issue will be resolved
Each and everytime we need to follow this same process not just once, each
and everytime when we create a new table not column
--
Ticket URL: <https://code.djangoproject.com/ticket/25100>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: sachinvettithanam | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Keywords: contentype migration | Triage Stage: Unreviewed
Has patch: 0 | Easy pickings: 0
UI/UX: 0 |
Changes (by sachinvettithanam):
* Attachment "Screen Shot 2015-07-10 at 6.07.48 pm copy.jpg" added.
Migration error responce
Django
when upgrading to 1.8 (skipping 1.7)
--------------------------------------+------------------------------------
Reporter: sachinvettithanam | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | Resolution:
Keywords: contentype migration | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by timgraham):
* needs_better_patch: => 0
* component: Migrations => Documentation
* needs_tests: => 0
* needs_docs: => 0
* type: Bug => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
Please see if https://groups.google.com/d/topic/django-
users/DlRQOdsJL6o/discussion helps. Are you faking the contenttypes
migrations which causes both 0001 and 0002 to be faked? Maybe we could add
a tip about this in the 1.8 release notes since it seems to be a common
issue. `migrate --fake-initial` might resolve that.
--
Ticket URL: <https://code.djangoproject.com/ticket/25100#comment:1>
Django
when upgrading to 1.8 (skipping 1.7)
--------------------------------------+------------------------------------
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | Resolution:
Keywords: contentype migration | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by sachinvettithanam):
No i am not faking it
This is what really happens in 1.8
i try migrate --fake-initial - it didnt work
Response:
It says Your models have changes that are not yet reflected in a
migration, and so won't be applied.
Run 'manage.py makemigrations' to make new migrations, and then re-run
'manage.py migrate' to apply them.
with the same bunch of contenttype errors
'''Only Solution i really found was Downgrading to 1.7.* and migrating
contenttypes individually'''
migrate contenttypes
Response will be the same
It says Your models have changes that are not yet reflected in a
migration, and so won't be applied.
Run 'manage.py makemigrations' to make new migrations, and then re-run
'manage.py migrate' to apply them.
but there wont be any errors and issue will be solves temporarily
Note: now we can goback to 1.8 and go on with the developments .
Migrations wont have any issue in 1.8 untill we add a new table(i didnt
find any issues with columns ). If we add new table we should again do the
same procedures .
--
Ticket URL: <https://code.djangoproject.com/ticket/25100#comment:2>
Django
when upgrading to 1.8 (skipping 1.7)
Reporter: sachinvettithanam | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 1.8
Severity: Normal | Resolution: needsinfo
Keywords: contentype | Triage Stage: Accepted
migration |
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Changes (by timgraham):
* status: new => closed
* resolution: => needsinfo
Comment:
I'm not sure what's going on, and I think we need a sample project to
reproduce the issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/25100#comment:3>
Django
when upgrading to 1.8 (skipping 1.7)
Reporter: sachinvettithanam | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | Resolution:
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
--------------------------------------+------------------------------------
Changes (by timgraham):
* status: closed => new
* resolution: needsinfo =>
* easy: 0 => 1
Comment:
Steps to reproduce:
1) Have a pre-1.7 project.
2) Upgrade to Django 1.8 (skipping 1.7) and run `manage.py migrate
--fake`.
3) Now, `0002_remove_content_type_name.py` will get fake-applied and the
`name` column in the `django_content_type` table won't be dropped.
We should recommend using `migrate --fake-initial` in the 1.8 release
notes for this case.
--
Ticket URL: <https://code.djangoproject.com/ticket/25100#comment:4>
Django
when upgrading to 1.8 (skipping 1.7)
--------------------------------------+------------------------------------
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | Resolution:
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by timgraham):
* has_patch: 0 => 1
Comment:
[https://github.com/django/django/pull/5506 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/25100#comment:5>
Django
when upgrading to 1.8 (skipping 1.7)
Reporter: sachinvettithanam | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: 1.8
Severity: Normal | Resolution:
migration | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
Changes (by claudep):
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/25100#comment:6>
Django
when upgrading to 1.8 (skipping 1.7)
-------------------------------------+-------------------------------------
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 1.8
Keywords: contentype | Triage Stage: Ready for
migration | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"81b55fb90078788bfdc064550f2ff9da2c79d3b6" 81b55fb]:
{{{
#!CommitTicketReference repository=""
revision="81b55fb90078788bfdc064550f2ff9da2c79d3b6"
Fixed #25100 -- Documented an upgrade caveat for contenttypes migration.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25100#comment:7>
Django
when upgrading to 1.8 (skipping 1.7)
-------------------------------------+-------------------------------------
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 1.8
Severity: Normal | Resolution: fixed
Keywords: contentype | Triage Stage: Ready for
migration | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"8b1c386f80638878f295860a26ecbd19d59cde9c" 8b1c386]:
{{{
#!CommitTicketReference repository=""
revision="8b1c386f80638878f295860a26ecbd19d59cde9c"
[1.9.x] Fixed #25100 -- Documented an upgrade caveat for contenttypes
migration.
Backport of 81b55fb90078788bfdc064550f2ff9da2c79d3b6 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25100#comment:8>
Django
when upgrading to 1.8 (skipping 1.7)
-------------------------------------+-------------------------------------
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 1.8
Severity: Normal | Resolution: fixed
Keywords: contentype | Triage Stage: Ready for
migration | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"052bd3f7e3be28d77ca9031b31f473dd721c1eb1" 052bd3f]:
{{{
#!CommitTicketReference repository=""
revision="052bd3f7e3be28d77ca9031b31f473dd721c1eb1"
[1.8.x] Fixed #25100 -- Documented an upgrade caveat for contenttypes
migration.
Backport of 81b55fb90078788bfdc064550f2ff9da2c79d3b6 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25100#comment:9>