#34820: Change the properties of ForeignObject object, such as blank, null, and
execute migrate to report an error
-----------------------------+--------------------------------------
Reporter: RelaxedDong | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 4.2
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => needsinfo
* component: Database layer (models, ORM) => Migrations
* needs_tests: 0 => 1
Comment:
I'm not sure how to you reach a field without a `column` in migrations. I
don't think you've explained the issue in enough detail to confirm a bug
in Django, can you provide a sample project or test case that reproduces
the issue?
--
Ticket URL: <https://code.djangoproject.com/ticket/34820#comment:3>
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/0107018a736beb16-ac31d096-aa61-44d0-ad34-76c30a4f6816-000000%40eu-central-1.amazonses.com.
