[Django] #25330: RuntimeError: Error creating new content types." when upgrading to 1.8: due to contenttype.name : Reference #25100

[Django]

#25330: RuntimeError: Error creating new content types." when upgrading to 1.8: due
to contenttype.name : Reference #25100
--------------------------------------+--------------------
Reporter: sachinvettithanam | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.contenttypes | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+--------------------
Found Issue started after :
Fixed #24099 -- Removed contenttype.name deprecated field

Now i dropped column name manually and the issue was resolved for ever
Tested : I couldnt recreate the senario again

'''ALTER TABLE django_content_type DROP COLUMN name'''

--
Ticket URL: <https://code.djangoproject.com/ticket/25330>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#25330: RuntimeError: Error creating new content types." when upgrading to 1.8: due
to contenttype.name : Reference #25100

-------------------------------------+-------------------------------------
Reporter: sachinvettithanam | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: | Version: 1.8
contrib.contenttypes |
Severity: Normal | Resolution: duplicate
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 timgraham):

* status: new => closed
* needs_better_patch: => 0
* resolution: => duplicate
* needs_tests: => 0
* needs_docs: => 0

Comment:

Duplicate of #25100. We are still seeking a way to reproduce the issue.

--
Ticket URL: <https://code.djangoproject.com/ticket/25330#comment:1>